What goharbor/harbor shipped

V2.16.0-rc2 is out: Valkey cache backend, multi-arch amd64+arm64, and a source column on artifact_accessory. Also landed: CSRF middleware replaced after CVE-2025-24358, IPv6 zone comparison fix, robot role assignment restored, and audit-log events for custom roles.

Harbor v2.16.0-rc2 is available, adding Valkey as the cache backend, full multi-architecture support for amd64 and arm64, and a source column on artifact_accessory. This week also includes security work: gorilla/csrf was replaced with net/http.CrossOriginProtection after CVE-2025-24358 was reported, SameOrigin now compares IPv6 zone identifiers exactly, and upload Location values are redacted in registry rejection errors. Robot member role assignment compatibility is restored with escalation checks intact, and custom role creation, updates, and deletion now emit audit-log events.

Harbor v2.16.0-rc1 is out with Valkey cache and multi-arch amd64/arm64 images. This week also fixed registry_id updates, release workflow Buildx permissions, installer arguments, and bumped Go to 1.26.10 on release-2.13 and release-2.15.

Harbor v2.16.0-rc1 is available, bringing Valkey as the cache backend, full multi-architecture images for amd64 and arm64, and a source column on artifact accessories. This week also fixed UpdateProject to reject registry_id changes with 400 Bad Request instead of returning 200 OK. The publish-release workflow now uses the runner's Docker engine to avoid a Buildx permission failure, and the release process preserves the empty installer argument. Go was bumped to 1.26.10 on release-2.13.0 and release-2.15.0, adding a crypto/x509 SPKI distrust list for compromised eMudhra intermediate CAs. ADDOPTERS was archived in favor of the community page.

This week: the replication resource filter works again, and the fix went back to 2.15. Replication now preserves artifact type for multi-tier accessories. Nil event data no longer panics the user audit resolver on 2.13 and 2.14. Go moved to 1.27.3 for the crypto/x509 fix.

This week in Harbor: replicated artifacts keep their correct type for multi-tier accessories, so signatures of an SBOM no longer inherit an UNKNOWN type from the accessory. The replication resource filter is applied again when fetching artifacts, and that fix was backported to 2.15. A panic in the user audit event resolver on nil event data for a PUT on the users collection is fixed on both the 2.13 and 2.14 branches. The bundled Trivy adapter binary now carries version info instead of placeholders, and Go moved to 1.27.3 to distrust compromised intermediate certificates.

This week: manifest body limits and decompression bounds close abuse paths, empty registryctl secrets are rejected, and cron expressions that can never fire no longer spin jobservice CPU. Event-triggered replication got a higher-priority queue, and task failures now surface error

This week in Harbor: manifest PUT bodies are capped at 4 MiB including chunked uploads, the CNAI parser bounds the bytes it actually unpacks, and registryctl rejects empty secrets. Upload Location headers are validated against the request origin, and cron expressions that can never fire no longer spin jobservice CPU. Event-triggered replication now runs in a dedicated higher-priority queue, and failed tasks record a status message that is exposed in the replication task API and shown in the UI.

Several patch releases shipped this week. Webhooks to internal addresses are blocked by default in the 2.13, 2.14 and 2.15 releases, then allowed by default again in the follow-ups, which add egress policy levels and an allowlist. Legacy signer pull is on by default.

This week Harbor published patch releases on several branches, and the headline change for operators is the webhook egress default. The fix for GHSA-2phj-cp9f-qq6w blocks webhook and Slack delivery to private, loopback, link-local and other non-public addresses, including hostnames that resolve to them such as *.svc.cluster.local, so webhooks to internal receivers stopped working after upgrade. The follow-up releases make private network access the default again, keep the setting configurable, and add three egress policy levels plus an allowlist instead of a single boolean. Content trust also defaults to allowing legacy signer pull so existing cosign and notation signing workflows keep working. Other fixes cover redaction of pagination links in rejection errors, the redis base image on the

Harbor updates: GC now uses current Redis config at runtime, custom project roles are available, and proxy cache stale content labeling is clearer. CI improvements prevent transient failures.

This week's Harbor updates focus on reliability and flexibility. Scheduled garbage collection now reads Redis configuration from the environment at runtime, so moves or password changes no longer break GC. Custom project roles join built-in roles for more granular access control. Proxy cache behavior is now more clearly documented. CI improvements make builds more resilient to transient network issues.

Harbor v2.15.3-rc2 is out. This release fixes retention policy metadata leaks, corrects GC freed space reporting, and improves error messages across the platform.

Harbor v2.15.3-rc2 is available. Key improvements include fixing retention policy metadata that leaked after project deletion, correcting garbage collection to accurately report freed space without counting missing blobs, and refining error messages for better clarity. These fixes improve data consistency and operational reliability.

Harbor's latest updates include retention settings for proxy-cache projects, RFC-compliant URL scheme checking, and fixes for cache handling and graceful shutdown behavior.

Harbor continues improving with this week's releases: retention settings are now configurable during proxy-cache project creation, URL scheme checking for CA downloads is now RFC 3986 compliant, cache prefix handling is fixed to prevent entry duplication, and graceful shutdown produces cleaner logs. Plus updated dependency management strategies for better CI stability.