A security vulnerability has been detected in adafap api-mcp up to 92b9a5d04acfec165c7d4ef852496593aa87be06. (CVE-2026-19374)
A server-side request forgery (SSRF) vulnerability exists in the adafap api-mcp component, specifically in the customAxios function within app/api/proxy/route.ts. The vulnerability allows remote attackers to manipulate the url argument, potentially causing the server to make unintended requests. The product uses a rolling release strategy, so specific affected versions are not provided. The issue was reported early but has not yet received a response from the project. The CVSS score is 7.3, indicating a medium severity level.
AI Analysis
Technical Summary
CVE-2026-19374 describes a server-side request forgery vulnerability in the adafap api-mcp up to commit 92b9a5d04acfec165c7d4ef852496593aa87be06. The flaw exists in the customAxios function of the Proxy API Endpoint component (file app/api/proxy/route.ts). By manipulating the url argument, an attacker can cause the server to perform unauthorized requests. The vulnerability is remotely exploitable without authentication. Due to the rolling release model, no fixed or affected version numbers are specified. The project has been notified but has not issued a patch or advisory.
Potential Impact
Successful exploitation allows an unauthenticated remote attacker to induce the server to make arbitrary requests, potentially accessing internal resources or services not otherwise accessible. This can lead to information disclosure, integrity loss, or availability impact depending on the target of the SSRF. The CVSS 3.1 base score of 7.3 reflects a moderate risk with network attack vector, low attack complexity, no privileges required, and impacts on confidentiality, integrity, and availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since the project has not responded or issued a fix, users should monitor official channels for updates. Until a fix is available, consider implementing network-level protections to restrict outbound requests from the affected service to trusted destinations only, if feasible.
A security vulnerability has been detected in adafap api-mcp up to 92b9a5d04acfec165c7d4ef852496593aa87be06. (CVE-2026-19374)
Description
A server-side request forgery (SSRF) vulnerability exists in the adafap api-mcp component, specifically in the customAxios function within app/api/proxy/route.ts. The vulnerability allows remote attackers to manipulate the url argument, potentially causing the server to make unintended requests. The product uses a rolling release strategy, so specific affected versions are not provided. The issue was reported early but has not yet received a response from the project. The CVSS score is 7.3, indicating a medium severity level.
CVSS v3.1
Score 7.3high
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-19374 describes a server-side request forgery vulnerability in the adafap api-mcp up to commit 92b9a5d04acfec165c7d4ef852496593aa87be06. The flaw exists in the customAxios function of the Proxy API Endpoint component (file app/api/proxy/route.ts). By manipulating the url argument, an attacker can cause the server to perform unauthorized requests. The vulnerability is remotely exploitable without authentication. Due to the rolling release model, no fixed or affected version numbers are specified. The project has been notified but has not issued a patch or advisory.
Potential Impact
Successful exploitation allows an unauthenticated remote attacker to induce the server to make arbitrary requests, potentially accessing internal resources or services not otherwise accessible. This can lead to information disclosure, integrity loss, or availability impact depending on the target of the SSRF. The CVSS 3.1 base score of 7.3 reflects a moderate risk with network attack vector, low attack complexity, no privileges required, and impacts on confidentiality, integrity, and availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since the project has not responded or issued a fix, users should monitor official channels for updates. Until a fix is available, consider implementing network-level protections to restrict outbound requests from the affected service to trusted destinations only, if feasible.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-g33v-9g6g-xm9p
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-19374"]
- Ecosystems
- []
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a79f0f4bf8831d539f646d0
Added to database: 08/10/2026, 15:40:36 UTC
Last enriched: 08/10/2026, 16:09:41 UTC
Last updated: 08/11/2026, 04:40:59 UTC
Views: 7
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.