The hostmatcher bypass in CVE-2026-59765 isn't an isolated security defect — it's the predictable failure mode of a security control built on top of a fundamentally contradictory architecture. Migration and import features must fetch content from user-supplied URLs to function, yet security demands they refuse most of those same URLs. The hostmatcher attempts to resolve this with a blocklist, but blocklists for SSRF have a documented half-life measured in bypass counts, not years. Jenkins, GitLab, Confluence, Atlassian Crowd — all followed the same trajectory: SSRF reported, host block added, bypass found, another block added, another bypass, until the allowlist becomes unmanageable. The pattern isn't vendor-specific; it's architectural. What's different now is the blast radius. The metadata endpoint at 169.254.169.254 (and cloud equivalents) transforms this from a file read into a credential pivot — the attacker who bypasses the hostmatcher can potentially obtain keys that reach every cloud resource that workload touches. That's not a rounding error; it's a single failure mode that detonates across your entire infrastructure plane. The fix that patches this bypass without addressing the retrieval architecture will produce CVE-2027-XXXX through a different vector. That's not prophecy — it's the documented pattern of this vulnerability class across two decades. What you should do: audit every migration, import, and fetch feature in your environment for URL-fetching with access to internal networks. Check whether the retrieval process can reach cloud metadata endpoints, internal service discovery, or management interfaces. Treat any 'hostmatcher' or blocklist-based SSRF control you find as temporary and plan for structural isolation instead — either by moving to content-addressed retrieval where the migration tool never initiates outbound connections, or by network-segmenting the retrieval process so its blast radius is bounded regardless of bypass. The organizational question is whether your security development lifecycle has any mechanism to recognize the blocklist pattern as terminal rather than merely ongoing. If you're still adding blocks to a list, you're not fixing the architecture — you're managing decline.
CVE-2026-59765
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 · uneditedSSRF via Migration Asset Downloads Bypasses hostmatcher — Reads Internal Files and Cloud Metadata
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 $8,000. 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-59765 — 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 sourcesThe hostmatcher bypass in CVE-2026-59765 isn't an isolated security defect — it's the predictable failure mode of a security control built on top of a fundamentally contradictory architecture. Migration and import features must fetch content from user-supplied URLs to function, yet security demands they refuse most of those same URLs. The hostmatcher attempts to resolve this with a blocklist, but blocklists for SSRF have a documented half-life measured in bypass counts, not years. Jenkins, GitLab, Confluence, Atlassian Crowd — all followed the same trajectory: SSRF reported, host block added, bypass found, another block added, another bypass, until the allowlist becomes unmanageable. The pattern isn't vendor-specific; it's architectural. What's different now is the blast radius. The metadata endpoint at 169.254.169.254 (and cloud equivalents) transforms this from a file read into a credential pivot — the attacker who bypasses the hostmatcher can potentially obtain keys that reach every cloud resource that workload touches. That's not a rounding error; it's a single failure mode that detonates across your entire infrastructure plane. The fix that patches this bypass without addressing the retrieval architecture will produce CVE-2027-XXXX through a different vector. That's not prophecy — it's the documented pattern of this vulnerability class across two decades. What you should do: audit every migration, import, and fetch feature in your environment for URL-fetching with access to internal networks. Check whether the retrieval process can reach cloud metadata endpoints, internal service discovery, or management interfaces. Treat any 'hostmatcher' or blocklist-based SSRF control you find as temporary and plan for structural isolation instead — either by moving to content-addressed retrieval where the migration tool never initiates outbound connections, or by network-segmenting the retrieval process so its blast radius is bounded regardless of bypass. The organizational question is whether your security development lifecycle has any mechanism to recognize the blocklist pattern as terminal rather than merely ongoing. If you're still adding blocks to a list, you're not fixing the architecture — you're managing decline.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-59765 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