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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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.

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 is the EPSS score for GHSA-q76j-58cx-wp5v?

GHSA-q76j-58cx-wp5v has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 59th 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-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.

Vulnerability in RPKI manifest validation

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs59th percentile — riskier than 59% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from 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

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 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`net.ripe.rpki:rpki-validator-3:3.2-2020.10.28.23.06`

Affected Products

1 product · 1 configurations

Application

rpki validator 3ripe

≥ 3.0 && ≤ 3.1-2020.07.06.14.28

range

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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.

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?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

Vulnerability in RPKI manifest validationGHSA-q76j-58cx-wp5v