# Vulnerability in RPKI manifest validation

Advisory record · `GHSA-q76j-58cx-wp5v`

- **Identifiers:** `GHSA-q76j-58cx-wp5v` · `CVE-2020-16164`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html)
- **Tags:** [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md)
- **Published:** 13 Nov 2020
- **Updated:** 8 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 13 Nov 2020, 17:28 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `net.ripe.rpki:rpki-validator-3` (Maven): affected `<3.2-2020.10.28.23.06`; fixed in `3.2-2020.10.28.23.06`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Maven package net.ripe.rpki:rpki-validator-3 before 3.2-2020.10.28.23.06 is vulnerable to flaws in RPKI manifest validation, where objects listed on a manifest can be hidden or expired objects can be replayed. An attacker performing a man-in-the-middle attack on the TLS connection to an RRDP repository, or on an rsync-only repository, could stop new ROAs from being received or selectively hide ROAs, causing routes to become INVALID. Upgrade to 3.2-2020.10.28.23.06 or later, which implements the RFC 6486bis validation methods and enables strict validation by default.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0091, the 60th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:19 UTC: First seen by agentprime
- 31 Oct 2026, 14:19 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-q76j-58cx-wp5v)

## Sources

- [GitHub Advisory Database: GHSA-q76j-58cx-wp5v](https://github.com/advisories/GHSA-q76j-58cx-wp5v)
- [OSV: GHSA-q76j-58cx-wp5v](https://osv.dev/vulnerability/GHSA-q76j-58cx-wp5v)
- <https://github.com/RIPE-NCC/rpki-validator-3/security/advisories/GHSA-q76j-58cx-wp5v>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-q76j-58cx-wp5v>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-q76j-58cx-wp5v/>. Everything for agents: <https://agentprime.io/llms.txt>.
