How severe is GHSA-3wpx-625q-22j7?

No CVSS score has been assigned to GHSA-3wpx-625q-22j7 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3wpx-625q-22j7?

GHSA-3wpx-625q-22j7 affects the following packages: harbor (Bitnami). Ecosystems affected: Bitnami.

How do I fix GHSA-3wpx-625q-22j7?

Update harbor to 2.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3wpx-625q-22j7 is resolved across your whole dependency graph.

How do I detect GHSA-3wpx-625q-22j7 in my Bitnami dependencies?

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

How do I mitigate GHSA-3wpx-625q-22j7 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-3wpx-625q-22j7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-3wpx-625q-22j7 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.

What is the EPSS score for GHSA-3wpx-625q-22j7?

GHSA-3wpx-625q-22j7 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 23th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-3wpx-625q-22j7?

GHSA-3wpx-625q-22j7 is classified as CWE-285 (CWE-285), CWE-863 (CWE-863). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-3wpx-625q-22j7 published, and has it been updated?

GHSA-3wpx-625q-22j7 was published on November 20, 2024 and was last updated on September 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.

User permission validation failure and disclosure of P2P…

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-3wpx-625q-22j7.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs23th percentile — riskier than 23% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

📦harbor

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

Description

Harbor fails to validate the user permissions when updating p2p preheat policies. By sending a request to update a p2p preheat policy with an id that belongs to a project that the currently authenticated user doesn't have access to, the attacker could modify p2p preheat policies configured in other projects.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Bitnami	`harbor`	≥ 2.0.0&&< 2.4.3	2.4.3

Affected Products

1 product · 2 configurations

Application

harborlinuxfoundation

≥ 2.5.0 && < 2.5.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for harbor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update harbor to 2.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3wpx-625q-22j7 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

Harbor fails to validate the user permissions when updating p2p preheat policies. By sending a request to update a p2p preheat policy with an id that belongs to a project that the currently authenticated user doesn't have access to, the attacker could modify p2p preheat policies configured in other projects.

O3 Security · Impact-Aware SCA

Is GHSA-3wpx-625q-22j7 in your dependencies?

Find it across Bitnami, including transitive dependencies.

Scan my dependencies How O3 SCA works

User permission validation failure and disclosure of P2P preheat execution logsGHSA-3wpx-625q-22j7