Host-local data disclosure via unvalidated token realm
Published Apr 1, 2026 · Updated Apr 1, 2026
SSRF in Docker Model Runner before 1.1.25 allows attackers to read host-local service responses through a malicious OCI registry. The OCI token exchange follows an unvalidated realm URL from WWW-Authenticate, returns the resulting GET response body, and can relay it in a Bearer token. Exploitation requires a pull from an attacker-controlled registry or access from an unprivileged container; ECI blocks container access unless host-side TCP exposure remains enabled.
Summary
What happened
SSRF in Docker Model Runner before 1.1.25 allows attackers to read host-local service responses through a malicious OCI registry. The OCI token exchange follows an unvalidated realm URL from WWW-Authenticate, returns the resulting GET response body, and can relay it in a Bearer token. Exploitation requires a pull from an attacker-controlled registry or access from an unprivileged container; ECI blocks container access unless host-side TCP exposure remains enabled.
The record
- CVE
- CVE-2026-33990
- Published
- Apr 1, 2026
- Updated
- Apr 1, 2026
- Vendor
- Docker
- Product
- Docker Model Runner
- Classifications
- CWE-918, T1090
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 1, 2026CVE publishedPublication date reported by the CVE source.
- Apr 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.1.25
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo