CVE-2026-2249
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 · uneditedMETIS DFS devices (versions <= oscore 2.1.234-r18) expose a web-based shell at the /console endpoint that does not require authentication. Accessing this endpoint allows a remote attacker to execute arbitrary operating system commands with 'daemon' privileges. This results in the compromise of the software, granting unauthorized access to modify configuration, read and alter sensitive data, or disrupt services.
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 confidenceMETIS DFS devices running oscore version 2.1.234-r18 or earlier contain an unauthenticated command injection vulnerability in the /console web endpoint. This endpoint exposes a web-based shell that accepts and executes arbitrary operating system commands without requiring any authentication, running with 'daemon' user privileges.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 METIS DFS deviceConfirm the target system is a METIS DFS device by checking the device model, firmware branding, or system information via 'uname -a', 'cat /proc/version', or the device's web interface header.Affected if The device is a METIS DFS appliance.
-
Check oscore versionRetrieve the oscore version by logging into the device via SSH or console and running 'oscore --version' or checking '/etc/oscore-version' if available. Alternatively, check via the web interface firmware version display.Affected if The oscore version is 2.1.234-r18 or earlier.
-
Verify /console endpoint accessibilityAttempt to access the /console endpoint by sending an HTTP GET request to 'http://<device-ip>/console' or 'https://<device-ip>/console' from an authorized network location.Affected if The /console endpoint responds with a web shell or login prompt without requiring authentication.
-
Check for web shell functionalityIf the /console endpoint is accessible, inspect the page source or interact with the endpoint to confirm it exposes a command input field or shell interface for executing OS commands.Affected if The /console endpoint provides a web-based shell interface that accepts and executes operating system commands.
A system is affected if it is a METIS DFS device running oscore version 2.1.234-r18 or earlier with the /console web endpoint exposed and functional.
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 dataUpgrade METIS DFS firmware to a version newer than oscore 2.1.234-r18. If no patched version is available, immediately restrict network access to the /console endpoint using firewall rules or network segmentation to prevent unauthorized external access.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2249 — 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-2249 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