How severe is GHSA-q76j-58cx-wp5v?

No CVSS score has been assigned to GHSA-q76j-58cx-wp5v yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-q76j-58cx-wp5v?

GHSA-q76j-58cx-wp5v affects the following packages: net.ripe.rpki:rpki-validator-3 (Maven). Ecosystems affected: Maven.

How do I fix GHSA-q76j-58cx-wp5v?

Update net.ripe.rpki:rpki-validator-3 to 3.2-2020.10.28.23.06 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q76j-58cx-wp5v is resolved across your whole dependency graph.

How do I detect GHSA-q76j-58cx-wp5v in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for net.ripe.rpki:rpki-validator-3. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-q76j-58cx-wp5v 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.

How does O3 Security protect against GHSA-q76j-58cx-wp5v?

O3 pinpoints whether GHSA-q76j-58cx-wp5v is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-q76j-58cx-wp5v actively exploited in the wild?

No public exploit code has been indexed for GHSA-q76j-58cx-wp5v 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 type of vulnerability is GHSA-q76j-58cx-wp5v?

GHSA-q76j-58cx-wp5v is classified as CWE-295 (CWE-295). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-q76j-58cx-wp5v published, and has it been updated?

GHSA-q76j-58cx-wp5v was published on November 13, 2020 and was last updated on July 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.

☕ Maven

Not in CISA KEV

GHSA-q76j-58cx-wp5v

GHSA-q76j-58cx-wp5v is a CWE-295 vulnerability in net.ripe.rpki:rpki-validator-3. O3 Security confirms whether GHSA-q76j-58cx-wp5v is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Vulnerability in RPKI manifest validation

Also known asCVE-2020-16164

Published

Nov 13, 2020

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Real-World Exposure

1 pkg affected

☕net.ripe.rpki:rpki-validator-3

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

Description

To exploit this vulnerability, an attacker would need to perform a man in the middle attack on the TLS connection between the validator and an RRDP repository or perform a man in the middle attack against a rsync-only repository.

The update addresses the vulnerability by implementing validation methods from RFC 6486bis and enabling strict validation by default.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`net.ripe.rpki:rpki-validator-3`	all versions	3.2-2020.10.28.23.06

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for net.ripe.rpki:rpki-validator-3. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update net.ripe.rpki:rpki-validator-3 to 3.2-2020.10.28.23.06 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q76j-58cx-wp5v 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.
How O3 protects you
O3 pinpoints whether GHSA-q76j-58cx-wp5v is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-q76j-58cx-wp5v. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A vulnerability in RPKI manifest validation exists when objects on the manifest are hidden, or expired objects are replayed. An attacker successfully exploiting this vulnerability could prevent new ROAs from being received or selectively hide ROAs, causing routes to become INVALID. To exploit this vulnerability, an attacker would need to perform a man in the middle attack on the TLS connection between the validator and an RRDP repository or perform a man in the middle attack against a rsync-only repository. The update addresses the vulnerability by implementing validation methods from [RFC

O3 Security · Impact-Aware SCA

Is GHSA-q76j-58cx-wp5v in your dependencies?

O3 detects GHSA-q76j-58cx-wp5v across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works