CVE-2026-25904: CWE-918 Server-Side Request Forgery (SSRF)
CVE-2026-25904 is a Server-Side Request Forgery (SSRF) vulnerability in the Pydantic-AI MCP Run Python tool, which uses an overly permissive Deno sandbox configuration. This misconfiguration allows Python code executed within the sandbox to access the localhost interface of the host system, potentially enabling SSRF attacks. The project is archived and unlikely to receive a fix, increasing risk for users who continue to rely on it. The vulnerability has a CVSS score of 5. 8 (medium severity), reflecting moderate impact and exploitation complexity. Exploitation requires user interaction but no privileges or authentication. While no known exploits are currently in the wild, the vulnerability could allow attackers to access internal services, leading to information disclosure and limited integrity and availability impacts. European organizations using this tool or similar configurations should be cautious, especially those in countries with strong adoption of Python and Deno-based development environments. Mitigation involves discontinuing use of the vulnerable tool, isolating sandbox environments, and restricting network access from sandboxed code. Countries with significant tech sectors and software development communities, such as Germany, France, the UK, and the Netherlands, are most likely to be affected.
AI Analysis
Technical Summary
CVE-2026-25904 is a Server-Side Request Forgery (SSRF) vulnerability classified under CWE-918, found in the Pydantic-AI MCP Run Python tool. This tool configures the Deno sandbox environment with overly permissive network access, allowing Python code executed within the sandbox to make requests to the localhost interface of the host machine. SSRF vulnerabilities enable attackers to induce the server-side application to send crafted requests to internal or external systems that would otherwise be inaccessible, potentially exposing sensitive information or enabling further attacks. The vulnerability arises because the sandbox does not properly restrict network access, violating the principle of least privilege. The project is archived, meaning no patches or fixes are expected, leaving users exposed if they continue to use this tool. The CVSS v3.1 base score is 5.8, indicating a medium severity level. The vector indicates network attack vector (AV:N), high attack complexity (AC:H), no privileges required (PR:N), user interaction required (UI:R), scope changed (S:C), and low impact on confidentiality, integrity, and availability (C:L/I:L/A:L). Although no known exploits are reported in the wild, the vulnerability could be exploited by tricking a user into executing malicious Python code within the sandbox, which then performs SSRF attacks against internal services. This can lead to information disclosure or limited disruption of internal services. The vulnerability highlights the risks of misconfigured sandbox environments, especially when running untrusted or semi-trusted code.
Potential Impact
For European organizations, the impact of CVE-2026-25904 depends largely on their use of the Pydantic-AI MCP Run Python tool or similar sandbox configurations. Organizations relying on this tool for Python code execution in isolated environments may be exposed to SSRF attacks that can access internal network services, potentially leading to unauthorized information disclosure or reconnaissance. This can facilitate lateral movement or further exploitation within the network. Although the impact on integrity and availability is rated low, the confidentiality breach could expose sensitive internal APIs or services. The archived status of the project means no official patches will be released, increasing the risk for organizations that continue to use it. European companies in sectors such as software development, cloud services, and research institutions that use Deno or Python sandboxing tools are particularly at risk. The requirement for user interaction limits automated exploitation but does not eliminate risk, especially in environments where users execute untrusted code. The medium severity rating suggests that while the threat is not critical, it warrants attention to prevent potential internal network compromises.
Mitigation Recommendations
1. Discontinue use of the Pydantic-AI MCP Run Python tool immediately, especially in production or sensitive environments, since it is archived and will not receive patches. 2. If continued use is necessary, isolate the sandbox environment using strict network segmentation and firewall rules to prevent access to localhost or internal network interfaces. 3. Employ network-level controls such as egress filtering to block unauthorized outbound requests from sandboxed processes. 4. Review and harden sandbox configurations to enforce the principle of least privilege, explicitly denying network access unless absolutely required. 5. Use alternative, actively maintained sandboxing tools with robust security controls and regular updates. 6. Implement monitoring and alerting for unusual network requests originating from sandboxed environments to detect potential SSRF attempts. 7. Educate developers and users about the risks of executing untrusted code and require code review or validation before execution. 8. Conduct regular security assessments of sandbox configurations and network access controls to identify and remediate similar misconfigurations.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland
CVE-2026-25904: CWE-918 Server-Side Request Forgery (SSRF)
Description
CVE-2026-25904 is a Server-Side Request Forgery (SSRF) vulnerability in the Pydantic-AI MCP Run Python tool, which uses an overly permissive Deno sandbox configuration. This misconfiguration allows Python code executed within the sandbox to access the localhost interface of the host system, potentially enabling SSRF attacks. The project is archived and unlikely to receive a fix, increasing risk for users who continue to rely on it. The vulnerability has a CVSS score of 5. 8 (medium severity), reflecting moderate impact and exploitation complexity. Exploitation requires user interaction but no privileges or authentication. While no known exploits are currently in the wild, the vulnerability could allow attackers to access internal services, leading to information disclosure and limited integrity and availability impacts. European organizations using this tool or similar configurations should be cautious, especially those in countries with strong adoption of Python and Deno-based development environments. Mitigation involves discontinuing use of the vulnerable tool, isolating sandbox environments, and restricting network access from sandboxed code. Countries with significant tech sectors and software development communities, such as Germany, France, the UK, and the Netherlands, are most likely to be affected.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-25904 is a Server-Side Request Forgery (SSRF) vulnerability classified under CWE-918, found in the Pydantic-AI MCP Run Python tool. This tool configures the Deno sandbox environment with overly permissive network access, allowing Python code executed within the sandbox to make requests to the localhost interface of the host machine. SSRF vulnerabilities enable attackers to induce the server-side application to send crafted requests to internal or external systems that would otherwise be inaccessible, potentially exposing sensitive information or enabling further attacks. The vulnerability arises because the sandbox does not properly restrict network access, violating the principle of least privilege. The project is archived, meaning no patches or fixes are expected, leaving users exposed if they continue to use this tool. The CVSS v3.1 base score is 5.8, indicating a medium severity level. The vector indicates network attack vector (AV:N), high attack complexity (AC:H), no privileges required (PR:N), user interaction required (UI:R), scope changed (S:C), and low impact on confidentiality, integrity, and availability (C:L/I:L/A:L). Although no known exploits are reported in the wild, the vulnerability could be exploited by tricking a user into executing malicious Python code within the sandbox, which then performs SSRF attacks against internal services. This can lead to information disclosure or limited disruption of internal services. The vulnerability highlights the risks of misconfigured sandbox environments, especially when running untrusted or semi-trusted code.
Potential Impact
For European organizations, the impact of CVE-2026-25904 depends largely on their use of the Pydantic-AI MCP Run Python tool or similar sandbox configurations. Organizations relying on this tool for Python code execution in isolated environments may be exposed to SSRF attacks that can access internal network services, potentially leading to unauthorized information disclosure or reconnaissance. This can facilitate lateral movement or further exploitation within the network. Although the impact on integrity and availability is rated low, the confidentiality breach could expose sensitive internal APIs or services. The archived status of the project means no official patches will be released, increasing the risk for organizations that continue to use it. European companies in sectors such as software development, cloud services, and research institutions that use Deno or Python sandboxing tools are particularly at risk. The requirement for user interaction limits automated exploitation but does not eliminate risk, especially in environments where users execute untrusted code. The medium severity rating suggests that while the threat is not critical, it warrants attention to prevent potential internal network compromises.
Mitigation Recommendations
1. Discontinue use of the Pydantic-AI MCP Run Python tool immediately, especially in production or sensitive environments, since it is archived and will not receive patches. 2. If continued use is necessary, isolate the sandbox environment using strict network segmentation and firewall rules to prevent access to localhost or internal network interfaces. 3. Employ network-level controls such as egress filtering to block unauthorized outbound requests from sandboxed processes. 4. Review and harden sandbox configurations to enforce the principle of least privilege, explicitly denying network access unless absolutely required. 5. Use alternative, actively maintained sandboxing tools with robust security controls and regular updates. 6. Implement monitoring and alerting for unusual network requests originating from sandboxed environments to detect potential SSRF attempts. 7. Educate developers and users about the risks of executing untrusted code and require code review or validation before execution. 8. Conduct regular security assessments of sandbox configurations and network access controls to identify and remediate similar misconfigurations.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- JFROG
- Date Reserved
- 2026-02-08T11:19:42.864Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6989a2774b57a58fa13a5753
Added to database: 2/9/2026, 9:01:43 AM
Last enriched: 2/16/2026, 1:34:11 PM
Last updated: 3/26/2026, 6:24:18 AM
Views: 145
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.