GPU VulnDB

Database/Container, Kubernetes & orchestration

Harbor: webhook targets not validated, allowing SSRF to internal and cloud metadata addresses

CVSS 8.5CVE-2026-111590Container, Kubernetes & orchestrationcurated

Impact

Harbor's webhook delivery accepts private and link-local target addresses. A ProjectAdmin can point a webhook policy at an internal address. When a project event fires, the jobservice sends an HTTP POST to that address from inside the network. If the target answers with an error status, the response body is written to the webhook execution log, which project members can read. On a shared registry that serves many GPU tenants, a project admin who is a tenant can probe the internal network and may read cloud metadata or other resources reachable only from the registry host.

Who can reach it

Authenticated user with ProjectAdmin rights on any Harbor project. They need network access to the Harbor API and must trigger a project event, such as pushing an image.

What to do

Upgrade Harbor to the fixed release listed in GHSA-2phj-cp9f-qq6w. The record does not give a version. This means upgrading the Harbor deployment and restarting its services, with a short registry outage unless Harbor runs HA. As a mitigation, block jobservice egress to link-local (169.254.0.0/16), metadata endpoints and internal management ranges, and review existing webhook policies for internal targets.

References

Related entries

All Container, Kubernetes & orchestration entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.