CVE-2026-33990 Vulnerability Analysis & Exploit Details

CVE-2026-33990
Vulnerability Scoring

9.1
/10
Critical Risk

As a catastrophic security flaw, CVE-2026-33990 has severe implications, demanding immediate intervention.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-33990 Details

Status: Analyzed

Last updated: 🕗 14 Apr 2026, 20:08 UTC
Originally published on: 🕔 01 Apr 2026, 17:28 UTC

Time between publication and last update: 13 days

CVSS Release: version 3

CVSS3 Source

134c704f-9b21-4f2e-91b3-4a467353bcc0

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2026-33990 Vulnerability Summary

CVE-2026-33990: Docker Model Runner (DMR) is software used to manage, run, and deploy AI models using Docker. Prior to version 1.1.25, 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. This issue has been patched in version 1.1.25. 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.

Assessing the Risk of CVE-2026-33990

Access Complexity Graph

The exploitability of CVE-2026-33990 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-33990

With low attack complexity and no required privileges, CVE-2026-33990 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-33990, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-33990, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2026-33990 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2026-33990 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: None
    CVE-2026-33990 does not impact system availability.

CVE-2026-33990 References

External References

CWE Common Weakness Enumeration

CWE-918

CAPEC Common Attack Pattern Enumeration and Classification

  • Server Side Request Forgery CAPEC-664 An adversary exploits improper input validation by submitting maliciously crafted input to a target application running on a server, with the goal of forcing the server to make a request either to itself, to web services running in the server’s internal network, or to external third parties. If successful, the adversary’s request will be made with the server’s privilege level, bypassing its authentication controls. This ultimately allows the adversary to access sensitive data, execute commands on the server’s network, and make external requests with the stolen identity of the server. Server Side Request Forgery attacks differ from Cross Site Request Forgery attacks in that they target the server itself, whereas CSRF attacks exploit an insecure user authentication mechanism to perform unauthorized actions on the user's behalf.

Vulnerable Configurations

  • cpe:2.3:a:docker:model_runner:1.0.0:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.0:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.0.1:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.1:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.0.2:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.2:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.0.3:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.3:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.0.4:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.4:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.0.5:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.5:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.0.6:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.6:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.0.7:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.7:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.0.8:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.8:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.0.9:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.9:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.0.10:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.10:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.0.11:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.11:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.0.12:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.12:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.0.13:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.13:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.0.14:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.14:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.0.15:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.15:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.0.16:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.16:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.0.17:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.17:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.0.18:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.18:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.0.19:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.19:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.0.20:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.20:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.0.21:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.21:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.0.22:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.22:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.0.23:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.23:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.0.24:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.24:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.0.25:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.25:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.0.26:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.26:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.0.27:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.27:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.0.28:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.28:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.0.29:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.29:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.0.30:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.0.30:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.1.0:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.1.0:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.1.1:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.1.1:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.1.2:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.1.2:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.1.3:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.1.3:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.1.4:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.1.4:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.1.5:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.1.5:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.1.6:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.1.6:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.1.7:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.1.7:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.1.8:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.1.8:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.1.9:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.1.9:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.1.10:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.1.10:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.1.11:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.1.11:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.1.12:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.1.12:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.1.13:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.1.13:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.1.14:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.1.14:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.1.15:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.1.15:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.1.16:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.1.16:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.1.17:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.1.17:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.1.18:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.1.18:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.1.19:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.1.19:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.1.20:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.1.20:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.1.21:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.1.21:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.1.22:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.1.22:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.1.23:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.1.23:*:*:*:*:docker:*:*
  • cpe:2.3:a:docker:model_runner:1.1.24:*:*:*:*:docker:*:*
    cpe:2.3:a:docker:model_runner:1.1.24:*:*:*:*:docker:*:*

Protect Your Infrastructure against CVE-2026-33990: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-6498 – The Five Star Restaurant Reservations plugin for WordPress is vulnerable to a payment bypass via PHP type juggling in versions up to, and including...
  • CVE-2026-42800 – NULL pointer dereference vulnerability in ASR1903 in ASR Lapwing_Linux on Linux (ims_client modules) allows Pointer Manipulation. This vulnerabil...
  • CVE-2026-41016 – Apache Airflow's SMTP provider `SmtpHook` called Python's `smtplib.SMTP.starttls()` without an SSL context, so no certificate validation was perfor...
  • CVE-2026-42799 – Out-of-bounds read vulnerability in ASR Kestrel (nr_fw modules) allows Overflow Buffers. This vulnerability is associated with program files Code...
  • CVE-2026-42512 – As dhclient is building an environment to pass to dhclient-script, it may need to resize the array of string pointers. The code which expands the ...