# CVE-2026-111590: SSRF in Harbor webhook delivery allows ProjectAdmin to reach internal services


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-2phj-cp9f-qq6w, GHSA-h7v4-fjg7-95fc

## What is CVE-2026-111590?

CVE-2026-111590 is a vulnerability in Harbor, published on 26 Oct 2026. 

### Official description

A wide range of Harbor versions allow SSRF via its webhook delivery component which does not properly validate web hook target addresses, allowing usage of private and link-local IP ranges. An authenticated attacker with ProjectAdmin permissions can configure a webhook policy pointing to a private internal address. When a project event fires, Harbor jobservice makes unauthenticated outbound HTTP POST requests to the target. If the target answers with an error status, the response body is written to the webhook execution log, which project members can read, potentially exposing cloud metadata or other network-restricted resources.

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


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

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

## Is CVE-2026-111590 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111590 is a vulnerability in Harbor, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-111590 in the wild and no public exploit code.

Affected product: Harbor. 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-111590/ (Markdown: https://insights.sbomify.com/CVE-2026-111590/index.md)
```

## Sources

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

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