CVE
OpsTree REMS through 1.0.0 Authentication Bypass via is_local_auth Flag
Affects OpsTree REMS version 1.0.0 and earlier, where the login endpoint trusts the client-controlled is_local_auth field. No fixed release is listed in the checked facts.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: The checked facts name no workaround and no fixed release. They do not say whether limiting access to the login endpoint would reduce the risk.
- 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 is affected by an authentication bypass that lets a remote attacker log in without a password by setting a client-controlled is_local_auth field in a login request. Doing so gives the attacker valid tokens and SuperUser administrative access, with no login or user action needed.
Read the original description
OpsTree REMS through 1.0.0 contains an authentication bypass vulnerability that allows unauthenticated attackers to obtain valid JWTs by setting the client-controlled is_local_auth field. Attackers can send a POST /api/v1/user/login/ request for the admin account with an invalid password and is_local_auth true to gain SuperUser administrative access.
Who should check
Teams running OpsTree REMS version 1.0.0 or earlier, including anyone exposing its login 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
- Severity9.3/10CVSS 9.3
- 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 checked facts name no workaround and no fixed release. They do not say whether limiting access to the login endpoint would reduce the risk.
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-126768 (OpsTree REMS through 1.0.0 Authentication Bypass via is_local_auth Flag), 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-126768 (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):
- REMS version 1.0.0 or earlier (source: https://www.vulncheck.com/advisories/opstree-rems-through-1.0.0-authentication-bypass-via-is-local-auth-flag)
- The login endpoint trusts the client-controlled is_local_auth field (source: https://www.vulncheck.com/advisories/opstree-rems-through-1.0.0-authentication-bypass-via-is-local-auth-flag)
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-126768 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126768 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://opstree.com/rems-ai-powered-observability/
- https://www.vulncheck.com/advisories/opstree-rems-through-1.0.0-authentication-bypass-via-is-local-auth-flag
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-126768
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-126768"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- OpsTree Solutions REMS
through 1.0.0
Evidence 5
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-126768
Is CVE-2026-126768 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 login endpoint trusts the client-controlled is_local_auth field. Setting that field lets an attacker obtain valid JWTs and gain SuperUser administrative access, including through the admin account with an invalid password.Source: vulncheck.com
Which versions are affected by CVE-2026-126768?
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, from the first release through 1.0.0, are in the listed range. To check a installation, look up the installed REMS version and compare it with 1.0.0.Source: vulncheck.com
How do I fix CVE-2026-126768?
The checked facts list no fixed version, so no upgrade target can be given. Check the installed REMS version against the affected range and watch for a vendor fix.Source: vulncheck.com
What if there's no patch?
The checked facts name no workaround and no fixed release. They do not say whether limiting access to the login endpoint would reduce the risk.Source: vulncheck.com