This CVE presents as a straightforward SSRF in a document parsing function, but treating it as a medium-severity web vulnerability fundamentally mischaracterizes the risk. The vulnerable component is an MCP layer — a bridge between AI agents and external tools — and MCP layers operate under a different trust model than traditional code. When a function accepts a URL parameter, that parameter can be populated not just by direct HTTP manipulation but by conversational language, RAG context, or chained tool outputs. An attacker doesn't scan a port; they convince an AI agent to request 'internal-host/confidential.pdf' through natural dialogue. The agent, which likely holds cloud credentials, database access, or internal network privileges the developer never intended to expose, becomes the unwitting SSRF client making the request from inside the firewall with real credentials. That's not server-side request forgery — it's trust relationship hijack. Compounding this: the maintainer was notified early and has not engaged. For a traditional library, you'd fork and patch. For an MCP layer embedded in agent configurations, you face a structural remediation dead-end — the layer's specific output format and behavioral contracts may be woven into your workflow, and without a maintained fork, there's no clean upgrade path. The CVE will generate tickets routed to teams looking for a patch version that won't arrive. The distinction this note demands you internalize: this is not a vulnerability to remediate — it's a dependency to remove. The EPSS score and CVSS rating will classify this as monitorable; the actual risk is that every AI agent integrated with this layer represents a growing attack surface with no decay mechanism, because the exposure window doesn't narrow over time — it compounds with each new integration during the silent pre-response period. Model your AI agents' credential scope. If those agents have cloud access, internal API reach, or persistent conversation context, this SSRF transforms into a trust hijack with blast radius that scales with the agent's privileges, not the function's.
CVE-2026-19752
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability was found in EnzoVezzaro mcp-dominican-layer up to 39dd373786712650097ad31db27d5c477c8f9c82. This affects the function parse-pdf of the file src/index.ts of the component PDF Parsing. Performing a manipulation of the argument pdfUrl results in server-side request forgery. It is possible to initiate the attack remotely. The exploit has been made public and could be used. The project was informed of the problem early through an issue report but has not responded yet.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysisThe server can be induced to make requests to a URL an attacker controls, turning it into a proxy into internal networks and cloud metadata services. It's especially dangerous behind a trusted network boundary. The fix is strict allow-listing of destinations and blocking access to internal address ranges.
General guidance for the server-side request forgery (ssrf) class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataThere is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.
Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.
We develop and verify an original fix where the vendor hasn’t, from $7,100. Deployed to your staging first — never straight to production.
Scope it with usSee what else the community needs solved on the solutions-needed board.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-19752 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesThis CVE presents as a straightforward SSRF in a document parsing function, but treating it as a medium-severity web vulnerability fundamentally mischaracterizes the risk. The vulnerable component is an MCP layer — a bridge between AI agents and external tools — and MCP layers operate under a different trust model than traditional code. When a function accepts a URL parameter, that parameter can be populated not just by direct HTTP manipulation but by conversational language, RAG context, or chained tool outputs. An attacker doesn't scan a port; they convince an AI agent to request 'internal-host/confidential.pdf' through natural dialogue. The agent, which likely holds cloud credentials, database access, or internal network privileges the developer never intended to expose, becomes the unwitting SSRF client making the request from inside the firewall with real credentials. That's not server-side request forgery — it's trust relationship hijack. Compounding this: the maintainer was notified early and has not engaged. For a traditional library, you'd fork and patch. For an MCP layer embedded in agent configurations, you face a structural remediation dead-end — the layer's specific output format and behavioral contracts may be woven into your workflow, and without a maintained fork, there's no clean upgrade path. The CVE will generate tickets routed to teams looking for a patch version that won't arrive. The distinction this note demands you internalize: this is not a vulnerability to remediate — it's a dependency to remove. The EPSS score and CVSS rating will classify this as monitorable; the actual risk is that every AI agent integrated with this layer represents a growing attack surface with no decay mechanism, because the exposure window doesn't narrow over time — it compounds with each new integration during the silent pre-response period. Model your AI agents' credential scope. If those agents have cloud access, internal API reach, or persistent conversation context, this SSRF transforms into a trust hijack with blast radius that scales with the agent's privileges, not the function's.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-19752 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data