CVE-2026-126772
OpsTree REMS through 1.0.0 Comment Author Spoofing via Incident Comment API
OpsTree REMS through 1.0.0 contains an improper attribution vulnerability that allows authenticated users to post comments as the incident creator via POST /api/v1/incidents/{incident_id}/comment. Lower-privileged attackers can comment on incidents owned by users such as a Super User to impersonate them and corrupt the incident timeline and audit trail.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| REMS OpsTree Solutions |
≥ 0; ≤ 1.0.0 (affected, custom)
Other versions: unaffected |
CNA: VulnCheck |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 4.0 / 5.3 medium |
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 | CNA: VulnCheck |
| 3.1 / 4.3 medium |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N | CNA: VulnCheck |
Exploit evidence
- https://gist.github.com/neelkotnis/5a5c810e16a3f242f336198b32213629
exploit · CNA: VulnCheck
References
- https://gist.github.com/neelkotnis/5a5c810e16a3f242f336198b32213629CNA: VulnCheck · technical-description, exploit
- https://opstree.com/rems-ai-powered-observability/CNA: VulnCheck · product
- https://www.vulncheck.com/advisories/opstree-rems-through-1.0.0-comment-author-spoofing-via-incident-comment-apiCNA: VulnCheck · third-party-advisory
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.