Live › vulnerability › CVE-2026-111590
Go to dashboardHarbor's webhook delivery does not block private and link-local IP targets, so a project admin can point a webhook at internal services. Error response bodies from those targets are written to the webhook execution log, which project members can read, potentially exposing cloud metadata.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-26 14:30 UTC. All times on this page are UTC.
Teams running self-hosted Harbor registries where project admins can create webhook policies. Harbor instances on a cloud network with a metadata endpoint are the main concern. Instances with no project admins outside trusted staff, or with webhooks disabled, carry less risk.
No product ranges from the sources yet.
169.254.169.254Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-111590")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.