CVE-2026-22312
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe device has a webserver that exposes a REST API authenticated with a constant token. The unauthenticated API can be used by an attacker to get access to system settings, modify the configuration and execute some commands (e.g. system reboot).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe device's webserver exposes a REST API that uses a constant (static) authentication token, making authentication effectively non-existent. An unauthenticated attacker can access system settings, modify configurations, and execute commands including system reboot. This represents a fundamental authentication bypass vulnerability where the secret token is discoverable or hardcoded.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify webserver REST API presenceEnumerate network services on the device or review documentation to confirm a webserver exposing REST API endpoints exists. Look for HTTP/HTTPS listeners on common ports (80, 443, 8080).Affected if A REST API is exposed via HTTP/HTTPS on the device.
-
Locate authentication token configurationInspect configuration files, firmware images, or embedded filesystems for hardcoded authentication tokens. Search for static strings in binary firmware using tools like strings, grep, or binwalk. Review API client code or mobile apps if available for hardcoded Bearer tokens.Affected if A constant/static token string is found hardcoded in files, firmware, or client code.
-
Test unauthenticated API accessSend HTTP requests to REST API endpoints (such as /api/settings, /api/config, /api/reboot) without providing any Authorization header or with an arbitrary token. Observe if the request succeeds.Affected if API calls succeed without valid authentication, returning sensitive data or executing privileged actions.
-
Verify token reuse across sessionsCapture the authentication token from API traffic or configuration, then attempt to use the same token across multiple sessions or after a device reboot. Confirm the token remains unchanged.Affected if The same token value persists across sessions, reboots, or is shared across multiple devices.
-
Check for default or documented static tokensReview device documentation, release notes, or public vulnerability disclosures for mentioned default credentials or static API tokens. Compare any discovered tokens against these known values.Affected if The token matches a documented default value or is known to be static per vendor guidance.
The device is affected if its REST API accepts a hardcoded or static token and allows unauthenticated or pseudo-authenticated access to sensitive endpoints without requiring dynamic credentials.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace the constant token authentication with proper authentication mechanisms (e.g., dynamic session tokens, OAuth, or certificate-based auth). Implement proper access controls and consider adding rate limiting. Deploy via firmware update.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA5.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,216.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22312 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22312 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data