REMS vulnerabilities and CVEs

Known vulnerabilities affecting REMS, with exploit availability attached to each one, so you can tell a flaw someone has written code for from one nobody has.

7 vulnerabilities tracked.

9.3 OpsTree REMS through 1.0.0 contains an authentication bypass vulnerability that allows unauthenticated attackers to obtain valid JWTs by… CVE-2026-126768 11 Nov 2026
8.7 OpsTree REMS through 1.0.0 contains a missing authentication vulnerability that allows unauthenticated remote attackers to access… CVE-2026-126769 11 Nov 2026
5.3 OpsTree REMS through 1.0.0 contains an improper attribution vulnerability that allows authenticated users to post comments as the incident… CVE-2026-126772 11 Nov 2026
5.3 OpsTree REMS through 1.0.0 contains a server-side request forgery vulnerability that allows authenticated users to make the backend connect… CVE-2026-126770 11 Nov 2026
5.3 OpsTree REMS through 1.0.0 contains a prompt injection vulnerability that allows authenticated users to disclose the hidden system prompt… CVE-2026-126767 11 Nov 2026
5.3 OpsTree REMS through 1.0.0 contains an improper authorization vulnerability that allows authenticated users to set an incident's reporter… CVE-2026-126766 11 Nov 2026
5.1 OpsTree REMS through 1.0.0 contains a stored cross-site scripting vulnerability that allows authenticated attackers to inject scripts by… CVE-2026-126771 11 Nov 2026

What this covers

This feed accumulates forward from the day it started storing records, and a name search that finds nothing here is also looked up against the registers directly — so an older advisory resolves even when it predates the corpus. It is still a reading view, not a substitute for the vendor's own advisory, and absence from this page is not a statement that REMS is free of vulnerabilities.

Query this from an agent over MCP · Check a lockfile by version

REMS vulnerabilities and CVEs

What this covers

Other products tracked here