CVE-2026-111590: Harbor · Server-Side Request Forgery (SSRF)
Affects HarborSource CVE Database V5
Not known to be exploited : upgrade to 2.15.3 soon.
Data as of 26 Oct 2026, 16:53 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- Patch
- Available – fixed in 2.15.3, 2.14.5, 2.13.6
Exploitation evidence
Disclosed: evidence found.
CVE published 26 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| HarborHarbor | Affected
| Fixed in
|
| HarborHarbor | Affected
| Fixed in
|
| HarborHarbor | Affected
| Fixed in
|
GitHubgoharbor/harborpkg:github/goharbor/harborOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Fixed versions of Harbor are 2.15.3, 2.14.5, and 2.13.6. Users should upgrade to these versions to remediate the SSRF vulnerability. No other mitigation or temporary workaround is indicated in the available data.
Description
Harbor versions prior to 2.15.3, 2.14.5, and 2.13.6 contain a Server-Side Request Forgery (SSRF) vulnerability in the webhook delivery component. An authenticated attacker with ProjectAdmin permissions can configure webhooks to target internal private or link-local IP addresses. When triggered, Harbor's jobservice makes unauthenticated HTTP POST requests to these targets. If the target responds with an error, the response body is logged and accessible to project members, potentially exposing sensitive internal resources such as cloud metadata.