CVE-2026-72755

Routinator stores TA certificate in cache without validation

Published Oct 26, 2026 CVSS 3.1 · 3.8 Low EPSS < 1% KEV · Not listed
Description
Routinator stores a newly-retrieved TA certificate via HTTPS in cache without validation, potentially overwriting a known good TA certificate even if validation fails.

Analysis

AI-generated

Technical impact

Routinator, an open-source BGP Route Origin Authorization validator, caches Trust Anchor (TA) certificates retrieved via HTTPS without validating them. This flaw, classified as CWE-755, allows an attacker who can supply a malicious TA certificate to the software to overwrite an existing, valid certificate in the cache. The result is a potential loss of trust in routing data, as the cached TA would no longer be verified against a proven source. The vulnerability enables an integrity compromise of the certificate store, which could enable routing violations if the attacker’s certificate is accepted as authentic.

Affected Systems

The issue affects the NLnet Labs Routinator product. All installations earlier than version 0.15.3 are impacted. Versions 0.15.3 and later include the fix and are not vulnerable.

Risk and Exploitability

The CVSS score of 3.8 indicates moderate severity, and the EPSS score is unavailable, suggesting limited or unknown exploitation prevalence. The vulnerability is not listed in the CISA KEV catalogue, indicating no confirmed widespread exploitation. The likely attack path requires an attacker with the ability to inject a forged TA certificate over HTTPS to the Routinator instance; the lack of validation means the certificate will be stored unconditionally. Because the flaw is about data caching rather than remote code execution or privileged escalation, the exploitation risk is primarily local or network-based if the attacker can reach the server and present a malicious certificate payload.

Remediation

Vendor Solution

This issue is fixed in 0.15.3 and all later versions.


OpenCVE Recommended Actions

  • Upgrade Routinator to version 0.15.3 or later, which includes validation of cached TA certificates
  • Configure network defenses to block unauthorized HTTPS traffic to the Routinator server, limiting the ability of an adversary to supply a forged certificate
  • Audit the TA certificate store for unexpected changes; consider using an integrity monitoring tool or separate fingerprint repository to detect tampering

Generated by OpenCVE AI on October 26, 2026 at 19:37 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Nlnetlabs
Nlnetlabs routinator
Vendors & Products Nlnetlabs
Nlnetlabs routinator
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Routinator stores a newly-retrieved TA certificate via HTTPS in cache without validation, potentially overwriting a known good TA certificate even if validation fails.
Title Routinator stores TA certificate in cache without validation
Weaknesses CWE-755
References
Metrics cvssV3_1

{'score': 3.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:L'}

Weaknesses
  • CWE-755

    Improper Handling of Exceptional Conditions

Sources

Status
PUBLISHED
Assigner
NLnet Labs
Published
Updated
Oct 26, 2026, 5:57 PM
Reserved
Aug 10, 2026, 2:08 PM
Status
Deferred
Published
Oct 26, 2026, 6:18 PM
Modified
Oct 26, 2026, 6:35 PM