CVE-2026-126772: OpsTree Solutions REMS · Incorrect Authorization
Affects OpsTree Solutions REMSSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 11 Nov 2026, 18:35 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 5.3 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 4.3 |
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OpsTree SolutionsREMS | Affected
| Fixed in– |
AI-suggested
Since the vulnerability affects versions up to 1.0.0, users should monitor vendor advisories for updates or patches. Until a fix is available, restrict access to the commenting API to trusted users and consider additional application-layer authorization checks to prevent unauthorized comment posting.
Description
OpsTree Solutions REMS versions up to 1.0.0 have an authorization vulnerability that allows authenticated users with lower privileges to post comments as the incident creator on incidents they do not own. This improper attribution flaw enables attackers to impersonate higher-privileged users, such as Super Users, potentially corrupting incident timelines and audit trails.