How severe is GHSA-prh4-vhfh-24mj?

No CVSS score has been assigned to GHSA-prh4-vhfh-24mj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-prh4-vhfh-24mj?

GHSA-prh4-vhfh-24mj affects the following packages: github.com/goharbor/harbor (Go), github.com/goharbor/harbor (Go). Ecosystems affected: Go.

How do I fix GHSA-prh4-vhfh-24mj?

Update github.com/goharbor/harbor to 2.13.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-prh4-vhfh-24mj is resolved across your whole dependency graph.

How do I detect GHSA-prh4-vhfh-24mj in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/goharbor/harbor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-prh4-vhfh-24mj if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-prh4-vhfh-24mj actively exploited in the wild?

No public exploit code has been indexed for GHSA-prh4-vhfh-24mj yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-prh4-vhfh-24mj published, and has it been updated?

GHSA-prh4-vhfh-24mj was published on March 26, 2026 and was last updated on April 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

GHSA-prh4-vhfh-24mj — harbor

Fix: goharbor/harbor@85e7564

GHSA-prh4-vhfh-24mj is a security vulnerability in github.com/goharbor/harbor. A fix is available for github.com/goharbor/harbor — see the affected versions and patch details below.

Harbor: LDAP password and OIDC secret are not redacted in the audit log

Also known asGO-2026-4876

Published

Mar 26, 2026

Updated

Apr 8, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Apr 8, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🐹github.com/goharbor/harbor🐹github.com/goharbor/harbor

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Harbor write configuration payload to audit log when configuration change, the ldap_search_password and oidc_client_secret will be logged in the audit log without redacted

Patches

Harbor v2.15.0, v2.14.3, v2.13.5

Workarounds

Disable audit log configure event in Harbor Web Console: Go to Administration -> Configuration -> Enable Audit Log Event Type -> Uncheck "Update Configuration" and click "Save" Button.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/goharbor/harbor`	≥ 2.13.0&&< 2.13.5	2.13.5`go get github.com/goharbor/harbor@v2.13.5`
🐹Go	`github.com/goharbor/harbor`	≥ 2.14.0&&< 2.14.3	2.14.3`go get github.com/goharbor/harbor@v2.14.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/goharbor/harbor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/goharbor/harbor to 2.13.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-prh4-vhfh-24mj is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact Harbor write configuration payload to audit log when configuration change, the ldap_search_password and oidc_client_secret will be logged in the audit log without redacted ### Patches Harbor v2.15.0, v2.14.3, v2.13.5 ### Workarounds Disable audit log configure event in Harbor Web Console: Go to Administration -> Configuration -> Enable Audit Log Event Type -> Uncheck "Update Configuration" and click "Save" Button.

O3 Security · Impact-Aware SCA

Is GHSA-prh4-vhfh-24mj in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works