# CVE-2026-73432: Server-side request forgery in vulnerability-lookup

> An authenticated administrator can exploit SSRF in remote-instance synchronization to access internal services or cloud metadata endpoints.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-wx9v-ffw3-45wg

## What is CVE-2026-73432?

CVE-2026-73432 is a medium-severity server-side request forgery vulnerability in vulnerability-lookup, published on 12 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Vulnerability-Lookup contains a server-side request forgery (SSRF) vulnerability in the remote-instance synchronization functionality. Remote instance addresses were validated only for basic URL syntax before being stored, while the synchronization worker later dereferenced these addresses using requests.get() with automatic redirect handling and without enforcing network-boundary restrictions. 

An authenticated administrator with the admin:access permission could configure a remote instance whose address points to an internal, loopback, link-local, or cloud metadata HTTP(S) service. When synchronization is performed, the Vulnerability-Lookup server would issue the request from its own network context. An attacker could also use a publicly accessible URL that redirects to an internal destination, because redirects were previously followed without revalidating the destination.

Successful exploitation could allow a privileged attacker to probe or interact with services that are accessible from the Vulnerability-Lookup server but not directly reachable by the attacker, including private network services or cloud instance metadata endpoints. The exact confidentiality, integrity, or availability impact depends on the services reachable from the application server.

The patch introduces a shared outbound URL policy that restricts remote instances to HTTP(S), rejects non-public IP addresses, resolves hostnames at request time, and manually validates each redirect destination before following it.  The implementation explicitly blocks private, loopback, link-local, multicast, reserved, and unspecified addresses.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-73432?


## How do I fix CVE-2026-73432?

No fix has been published for CVE-2026-73432 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-73432 being exploited?

There is no known exploitation of CVE-2026-73432 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-73432 and fix it if it is affected.

What it is: CVE-2026-73432 is a medium-severity server-side request forgery vulnerability in vulnerability-lookup, published on 12 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-73432 in the wild and no public exploit code.

Affected product: vulnerability-lookup. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-73432/ (Markdown: https://insights.sbomify.com/CVE-2026-73432/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-73432
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-73432
- OSV: https://osv.dev/vulnerability/CVE-2026-73432

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-73432/
Summaries are generated and may contain mistakes; the official description above is the record.