CVE-2026-126766: OpsTree REMS through 1.0.0 Reporter Spoofing via /api/v1/incidents

Published Nov 11, 2026
·
Updated

OpsTree REMS through 1.0.0 contains an improper authorization vulnerability that allows authenticated users to set an incident's reporter to another user by supplying a client-controlled reporter field. Attackers can send crafted POST /api/v1/incidents or PATCH /api/v1/incidents/{id}/status requests to falsify incident attribution and corrupt the accountability audit trail.

Event History

Nov 11, 2026
CVE Published
via MITRE·06:11 PM
Data Sourced
via MITRE·06:11 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An authenticated OpsTree REMS user can exploit it. The attacker needs permission to submit incident creation or incident status update requests to the affected API endpoints.

2

What actions can an attacker perform?

An attacker can supply a client-controlled reporter value when sending POST requests to /api/v1/incidents or PATCH requests to /api/v1/incidents/{id}/status. This can attribute an incident to another user and compromise the accountability audit trail.

3

Which versions are affected?

OpsTree REMS through version 1.0.0 is affected.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203