CVE-2026-111590VulnerabilityPublished 26 Oct 2026

A wide range of Harbor versions allow SSRF via its webhook delivery component which does not properly validate web

Source GCVE Database

Authoritative record:CVE-2026-111590· High

Not known to be exploited : upgrade to 2.15.3 soon.

Data as of 26 Oct 2026, 17:05 UTC

Severity

High

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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-h7v4-fjg7-95fc

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
HarborHarbor	Affected >=2.15.0 <2.15.3	Fixed in 2.15.3
HarborHarbor	Affected >=2.14.0 <2.14.5	Fixed in 2.14.5
HarborHarbor	Affected >=1.7.0 <2.13.6	Fixed in 2.13.6
GitHubgoharbor/harbor`pkg:github/goharbor/harbor`Other threats	Affected <2.13.6 >=1.7.0 <2.14.5 >=2.14.0 <2.15.3 >=2.15.0	Fixed in 2.13.6 2.14.5 2.15.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, restrict ProjectAdmin permissions to trusted users only and monitor webhook configurations closely to prevent misuse. Avoid configuring webhooks to untrusted or internal IP ranges.

Description

Certain versions of Harbor contain a server-side request forgery (SSRF) vulnerability in the webhook delivery component. This flaw allows an authenticated attacker with ProjectAdmin permissions to configure webhook policies targeting private or link-local IP addresses. When triggered, Harbor's jobservice sends unauthenticated HTTP POST requests to these internal addresses. 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 services.

Impact

An attacker with ProjectAdmin permissions can leverage this SSRF vulnerability to access internal network resources that are normally inaccessible externally. The exposure of error response bodies in webhook execution logs may reveal sensitive data such as cloud metadata or other network-restricted information. This could facilitate further attacks or information leakage within the affected environment.

Summary

Harbor's webhook delivery component does not properly validate webhook target addresses, enabling SSRF attacks. An attacker with ProjectAdmin rights can exploit this by setting webhook policies to internal network addresses. Upon a project event, Harbor jobservice issues unauthenticated outbound HTTP POST requests to these targets. Error responses from these internal services are logged and visible to project members, risking exposure of sensitive internal information.

References

Community reviews

Loading reviews…