What is the CVSS score of CVE-2026-33990?

CVE-2026-33990 has a contested CVSS base score of 6.8 from a third party (e.g. CISA-ADP), while the vendor rates it Medium. vuln.today uses the vendor rating as authoritative.

Is there a patch available for CVE-2026-33990?

Yes, a patch is available for CVE-2026-33990. Update the affected software to the latest version immediately.

Docker CVE-2026-33990

EUVD-2026-17963 MEDIUM

Server-Side Request Forgery (SSRF) (CWE-918)

2026-03-30 https://github.com/docker/model-runner

GHSA-x2f5-332j-9xwq

Docker SSRF Microsoft Suse

Medium

Disputed · 6.8 NVD

Severity by source

Sources disagree (Medium–Critical)

GitHub Advisory PRIMARY

6.8 MEDIUM

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

SUSE

9.1 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.

CVSS VectorGitHub Advisory

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Patch released

Mar 31, 2026 - 21:13 nvd

Patch available

EUVD ID Assigned

Mar 30, 2026 - 17:15 euvd

EUVD-2026-17963

Analysis Generated

Mar 30, 2026 - 17:15 vuln.today

CVE Published

Mar 30, 2026 - 17:08 nvd

MEDIUM 6.8

DescriptionGitHub Advisory

Summary

Docker Model Runner contains an SSRF vulnerability in its OCI registry token exchange flow. When pulling a model, Model Runner follows the realm URL from the registry's WWW-Authenticate header without validating the scheme, hostname, or IP range. A malicious OCI registry can set the realm to an internal URL (e.g., http://127.0.0.1:3000/), causing Model Runner running on the host to make arbitrary GET requests to internal services and reflect the full response body back to the caller. Additionally, the token exchange mechanism can relay data from internal services back to the attacker-controlled registry via the Authorization: Bearer header.

Patches

Fixed in Docker Model Runner v1.1.25 Docker Desktop users should update to 4.67.0 or later, which includes the fixed Model Runner.

Workarounds

For Docker Desktop users, enabling Enhanced Container Isolation (ECI) blocks container access to Model Runner, preventing exploitation. However, if the Docker Model Runner is exposed to localhost over TCP in specific configurations, the vulnerability is still exploitable.

Impact

An unprivileged container or a malicious OCI registry that the user performed a pull from might issue GET requests to host-local services (localhost, internal network)

AnalysisAI

Server-side request forgery in Docker Model Runner allows unprivileged containers or malicious OCI registries to make arbitrary GET requests to internal services by exploiting unvalidated realm URLs in the OCI registry token exchange flow. Affected versions prior to 1.1.25 (Docker Desktop prior to 4.67.0) permit attackers to access host-local services and reflect response bodies back to the caller, potentially exfiltrating sensitive data from internal endpoints. No public exploit code or active exploitation has been reported at time of analysis.

Technical ContextAI

Docker Model Runner implements OCI registry authentication via the standard HTTP challenge mechanism defined in RFC 7235, where registries return a WWW-Authenticate header specifying a realm URL for token exchange. The vulnerability exists in the token exchange flow's failure to validate the realm URL's scheme, hostname, or IP range before making requests. The affected Go-based module (github.com/docker/model-runner) blindly follows attacker-controlled realm values, enabling Server-Side Request Forgery (SSRF, CWE-918). When Model Runner executes within a container or on a host, it can reach internal services typically isolated from untrusted workloads, and the token exchange mechanism can relay authentication data via the Authorization: Bearer header, creating a bidirectional data exfiltration channel.

RemediationAI

Vendor-released patch: Docker Model Runner v1.1.25 and later. Docker Desktop users must update to version 4.67.0 or later, which includes the fixed Model Runner. As a temporary workaround, Docker Desktop users can enable Enhanced Container Isolation (ECI) to block container access to Model Runner; however, this does not fully mitigate if Model Runner is exposed over TCP to localhost in specific network configurations. Users should prioritize patching to v1.1.25 or upgrading Docker Desktop to 4.67.0+. Refer to the official advisory at https://github.com/docker/model-runner/security/advisories/GHSA-x2f5-332j-9xwq for detailed patching guidance.