# OpsTree REMS through 1.0.0 Comment Author Spoofing via Incident Comment API

CVE record · `CVE-2026-126772`

- **Identifiers:** `CVE-2026-126772`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **CNA:** VulnCheck
- **Weakness (CWE):** [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Technologies:** [OpsTree Solutions REMS](https://agentprime.io/advisories/technology/opstree-solutions-rems.md)
- **Published:** 11 Nov 2026
- **Updated:** 13 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: VulnCheck) at 11 Nov 2026, 18:11 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: OpsTree Solutions. Product: REMS.
  - affected: `1.0.0 and earlier` (custom)
  - Other versions: unaffected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> OpsTree REMS through 1.0.0 has an improper attribution flaw in its incident comment API. An authenticated user, including a lower-privileged one, can post comments that appear to come from the incident creator, such as a Super User, which corrupts the incident timeline and audit trail. The source gives no fixed version or workaround.

Written 20 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 5.3 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`, from CNA (VulnCheck) (used for this record)
- 4.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`, from CNA (VulnCheck)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0031, the 24th percentile, on 22 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 11 Nov 2026, 18:11 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-126772)
- 11 Nov 2026, 18:21 UTC: First seen by agentprime
- 11 Nov 2026, 19:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-126772)

## Sources

- [CVE List: CVE-2026-126772](https://www.cve.org/CVERecord?id=CVE-2026-126772)
- [NVD: CVE-2026-126772](https://nvd.nist.gov/vuln/detail/CVE-2026-126772)

### References from the CNA

- <https://opstree.com/rems-ai-powered-observability/> (product)
- <https://www.vulncheck.com/advisories/opstree-rems-through-1.0.0-comment-author-spoofing-via-incident-comment-api> (third-party-advisory)
- <https://gist.github.com/neelkotnis/5a5c810e16a3f242f336198b32213629> (technical-description, exploit)

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-126772>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-126772/>. Everything for agents: <https://agentprime.io/llms.txt>.
