CVE-2026-39885: CWE-918: Server-Side Request Forgery (SSRF) in agentfront frontmcp
CVE-2026-39885 is a Server-Side Request Forgery (SSRF) vulnerability in the frontmcp product by agentfront, specifically in versions prior to 1. 0. 4. The vulnerability arises because the mcp-from-openapi library uses @apidevtools/json-schema-ref-parser to dereference $ref pointers in OpenAPI specifications without restricting URLs or using custom resolvers. This allows malicious OpenAPI specs to cause the server to fetch internal network resources, cloud metadata endpoints, or local files during initialization, enabling SSRF and local file read attacks. The vulnerability has a high severity with a CVSS score of 7. 5. No official patch or remediation level is explicitly stated in the provided data, but the description notes the issue is fixed in version 2. 3. 0 of the framework, which suggests upgrading to a fixed version is the recommended mitigation.
AI Analysis
Technical Summary
The frontmcp framework (agentfront) versions before 1.0.4 contain a SSRF vulnerability (CWE-918) due to the mcp-from-openapi library's use of @apidevtools/json-schema-ref-parser without URL restrictions when dereferencing $ref pointers in OpenAPI specs. This allows an attacker to supply a malicious OpenAPI specification that triggers server-side requests to internal or local resources during the initialize() call, potentially exposing sensitive internal network data or local files. The vulnerability is fixed in version 2.3.0 of the framework. The CVSS 3.1 score is 7.5 (high severity), reflecting network attack vector, low complexity, no privileges required, no user interaction, and high confidentiality impact.
Potential Impact
Successful exploitation can lead to unauthorized server-side requests to internal network addresses, cloud metadata endpoints, or local files, potentially exposing sensitive information. The confidentiality impact is high, but integrity and availability impacts are not indicated. There are no known exploits in the wild at this time.
Mitigation Recommendations
Upgrade to frontmcp version 2.3.0 or later, where this vulnerability is fixed. Since no official patch or temporary fix is explicitly provided in the vendor advisory, upgrading to the fixed version is the recommended remediation. Monitor vendor advisories for any additional guidance. No other mitigations are specified.
CVE-2026-39885: CWE-918: Server-Side Request Forgery (SSRF) in agentfront frontmcp
Description
CVE-2026-39885 is a Server-Side Request Forgery (SSRF) vulnerability in the frontmcp product by agentfront, specifically in versions prior to 1. 0. 4. The vulnerability arises because the mcp-from-openapi library uses @apidevtools/json-schema-ref-parser to dereference $ref pointers in OpenAPI specifications without restricting URLs or using custom resolvers. This allows malicious OpenAPI specs to cause the server to fetch internal network resources, cloud metadata endpoints, or local files during initialization, enabling SSRF and local file read attacks. The vulnerability has a high severity with a CVSS score of 7. 5. No official patch or remediation level is explicitly stated in the provided data, but the description notes the issue is fixed in version 2. 3. 0 of the framework, which suggests upgrading to a fixed version is the recommended mitigation.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The frontmcp framework (agentfront) versions before 1.0.4 contain a SSRF vulnerability (CWE-918) due to the mcp-from-openapi library's use of @apidevtools/json-schema-ref-parser without URL restrictions when dereferencing $ref pointers in OpenAPI specs. This allows an attacker to supply a malicious OpenAPI specification that triggers server-side requests to internal or local resources during the initialize() call, potentially exposing sensitive internal network data or local files. The vulnerability is fixed in version 2.3.0 of the framework. The CVSS 3.1 score is 7.5 (high severity), reflecting network attack vector, low complexity, no privileges required, no user interaction, and high confidentiality impact.
Potential Impact
Successful exploitation can lead to unauthorized server-side requests to internal network addresses, cloud metadata endpoints, or local files, potentially exposing sensitive information. The confidentiality impact is high, but integrity and availability impacts are not indicated. There are no known exploits in the wild at this time.
Mitigation Recommendations
Upgrade to frontmcp version 2.3.0 or later, where this vulnerability is fixed. Since no official patch or temporary fix is explicitly provided in the vendor advisory, upgrading to the fixed version is the recommended remediation. Monitor vendor advisories for any additional guidance. No other mitigations are specified.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-07T20:32:03.010Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69d6bfa81cc7ad14dab01ac0
Added to database: 4/8/2026, 8:50:48 PM
Last enriched: 4/16/2026, 12:15:26 PM
Last updated: 5/23/2026, 6:17:34 AM
Views: 79
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.
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.