CVE
OpsTree REMS through 1.0.0 Missing Authentication via /api/v1/databases Governance API
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: The facts do not describe a workaround. Limiting network access to the REMS Governance API so that /api/v1/databases is not reachable by untrusted clients is a general step that reduces exposure while no fix is available.
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 31/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
OpsTree REMS through 1.0.0 contains a missing authentication vulnerability that allows unauthenticated remote attackers to access Governance API endpoints, including /api/v1/databases. Attackers can send requests without an Authorization header, or with invalid or tampered JWT tokens, to retrieve stored database hosts, usernames, and passwords.
Who should check
Teams running OpsTree REMS version 1.0.0 or earlier, including any REMS deployment exposing the Governance API
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch5/5No patch listed yet
What would change the score
- Would score about 76 if added to CISA KEV
- Would score about 71 if CISA's SSVC rates exploitation active
- Would score about 36 if advisories confirm default setups are exposed
What to do
Workaround: The facts do not describe a workaround. Limiting network access to the REMS Governance API so that /api/v1/databases is not reachable by untrusted clients is a general step that reduces exposure while no fix is available.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126769 (OpsTree REMS through 1.0.0 Missing Authentication via /api/v1/databases Governance API), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126769 (entry last updated 2026-11-11):
Affected:
- OpsTree Solutions REMS: through 1.0.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Running REMS version 1.0.0 or earlier (source: https://www.vulncheck.com/advisories/opstree-rems-through-1.0.0-missing-authentication-via-api-v1-databases-governance-api)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-126769 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126769 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://gist.github.com/neelkotnis/3fc4a8587179a8691ed89056ea7df076
- https://opstree.com/rems-ai-powered-observability/
- https://www.vulncheck.com/advisories/opstree-rems-through-1.0.0-missing-authentication-via-api-v1-databases-governance-api
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126769
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126769"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- OpsTree Solutions REMS
through 1.0.0
Evidence 6
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Public exploit code · 1
Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
- Exploit
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126769
Is CVE-2026-126769 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The REMS Governance API at /api/v1/databases does not require authentication. Someone without a login can retrieve stored database hosts, usernames, and passwords.Source: vulncheck.com
Which versions are affected by CVE-2026-126769?
REMS: through 1.0.0.Source: cve.now feed data
Am I affected, and how do I check?
REMS version 1.0.0 and earlier are affected, per the listed range from the first release through 1.0.0. To check a deployment, look up the installed REMS version and confirm whether the /api/v1/databases endpoint is reachable.Source: vulncheck.com
How do I fix CVE-2026-126769?
No fixed version is listed in the checked facts, so no specific upgrade target can be named. Check the vendor's release channels for a newer version beyond 1.0.0.Source: vulncheck.com
What if there's no patch?
The facts do not describe a workaround. Limiting network access to the REMS Governance API so that /api/v1/databases is not reachable by untrusted clients is a general step that reduces exposure while no fix is available.Source: vulncheck.com