CVE-2026-2248
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 WIC 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 root (UID 0) privileges. This results in full system compromise, allowing unauthorized access to modify system configuration, read sensitive data, or disrupt device operations
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 WIC devices running oscore version 2.1.234-r18 or earlier contain an unauthenticated web-based shell at the /console endpoint. This endpoint allows remote attackers to bypass authentication entirely and execute arbitrary operating system commands with root (UID 0) privileges, leading to complete device compromise.
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 WIC deviceDetermine if the target device is a METIS WIC device by checking the device model, firmware branding, or startup banners. This can be done via device documentation, management interface, or console output during boot.Affected if The device is a METIS WIC device running the affected oscore software.
-
Check oscore versionLocate and retrieve the installed oscore version on the device. This may be available via firmware version display, system information pages, command line tools, or the device management interface. Compare the found version against 2.1.234-r18.Affected if The oscore version is 2.1.234-r18 or any earlier version.
-
Verify /console endpoint is accessibleAttempt to access the /console URL path on the device's web interface using HTTP or HTTPS. This can be done via curl, a browser, or a web vulnerability scanner from an external or internal network location.Affected if The /console endpoint responds and is reachable over the network.
-
Test /console authentication requirementSend a request to /console without providing any credentials or session cookies. Observe whether the endpoint returns a functional shell interface or requires login authentication.Affected if The /console endpoint returns a command shell or interface without requiring any authentication credentials.
A user is affected if they have a METIS WIC device running oscore version 2.1.234-r18 or earlier with an accessible and unauthenticated /console endpoint.
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 dataRestrict network access to the /console endpoint immediately through firewall rules or network segmentation. Contact the vendor for a patched firmware version and apply it at the earliest opportunity.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2248 — 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-2248 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