Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach exposed HTTP/RTR server over network
-
ExploitOpen many connections without closing
-
ExecutionExhaust available connection pool
-
ImpactHTTP server becomes unavailable
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A10:2025 - Mishandling of Exceptional Conditions
ASVS 5.0
V16 - Security Logging and Error Handling Exception handling procedures
|
| Exploitation Conditions | Exploitation requires that the operator has deliberately made Routinator's HTTP or RTR server reachable from an untrusted network; the vendor explicitly states the issue 'only affects users that make their HTTP or RTR server available to untrusted networks.' In a standard deployment where these endpoints are bound to trusted internal networks or localhost and reached only by the operator and RTR-speaking routers, the flaw is not remotely exposed. When exposed, no authentication, no user interaction, and no special configuration beyond that network reachability are needed - the attacker simply opens many connections that are never closed. The limiting factor is therefore deployment topology (untrusted-network exposure), not any attacker-side complexity. |
| Impact | This is a moderate-severity availability-only flaw (CWE-755, improper handling of exceptional conditions) whose signals are internally consistent and point to a real-but-bounded risk rather than an emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L, 5.3) correctly reflects a remotely triggerable, low-complexity, unauthenticated condition with no confidentiality or integrity impact and only partial availability loss - the HTTP server exhausts its connection pool and stops serving while the core RPKI validation process is not stated to crash. The vuln.today decision label is 'this_month' (not act_now/emergency), aligning with the modest impact. No EPSS score, no CISA KEV listing, and no PoC reference were provided, so exploitation probability signals are simply absent rather than conflicting. The single most important mitigating factor, stated by the vendor, is that the condition only affects deployments exposing the HTTP or RTR server to untrusted networks - Routinator is normally reached only by trusted internal RTR clients (routers) and operator tooling, so a correctly segmented deployment is not exposed. One cross-source discrepancy to verify: the reference advisory filename is CVE-2026-72756.txt while this record is CVE-2026-72757 - confirm with NLnet Labs that this advisory covers this CVE. Overall this is a legitimate but low-urgency availability issue, not a high-CVSS/low-real-risk mislabel nor a critical priority. |
| Exploit ScenarioDerived | An attacker who can reach a Routinator instance that has been exposed to an untrusted network opens a large number of TCP connections to the HTTP (or RTR) server and never closes them, exhausting the server's available connection slots. Because the vector is network-based, unauthenticated, and low-complexity (AV:N/AC:L/PR:N), no credentials or user interaction are needed; once the pool is exhausted, the HTTP server becomes unavailable to legitimate clients. No public exploit identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 26, 2026
Resource exhaustion in NLnet Labs Routinator lets an attacker make the validator's HTTP server unavailable by opening a large number of connections that are never closed, consuming its finite open-connection capacity (CVSS 5.3, availability-only). Only operators who deliberately expose Routinator's HTTP or RTR server to untrusted networks are reachable; in a standard deployment bound to localhost or trusted internal networks the flaw is not remotely exposed. No KEV listing and no public exploit identified at time of analysis, so urgency is driven by deployment topology rather than an active campaign.
RemediationAI
No vendor-released patch or fixed version was identified in the data available at time of analysis, so the first step is to check the NLnet Labs advisory at https://www.nlnetlabs.nl/downloads/routinator/CVE-2026-72756.txt for the corrected release and upgrade to it. Until then, the most effective control is to remove the exposure the vendor names: bind the HTTP and RTR listeners to loopback or a trusted management interface only, accepting that remote routers then lose direct RTR access unless it is tunnelled or proxied. Where remote access is required, allow-list the specific router and operator source addresses at the host firewall, with the trade-off that dynamic or NAT-ed peers need ongoing maintenance. Fronting the HTTP interface with a reverse proxy that enforces connection caps and idle timeouts adds an extra hop and a new failure point and does not cover the RTR service. Raising the process file-descriptor limit and shortening keep-alive/idle timeouts only widens the margin before exhaustion. Monitoring accepted connection counts for abnormal growth gives early warning of attempted abuse.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Routinator is NLnet Labs' Rust-based RPKI relying party validator: it collects and validates RPKI repositories and publishes the results through an HTTP interface and an RPKI-to-Router (RTR) service consumed by routers. The weakness is classed CWE-755 (Improper Handling of Exceptional Conditions): when peers open connections and never close them, the server does not reclaim those connection slots fast enough, so the process eventually runs out of open connections and refuses new ones, leaving the HTTP server unavailable. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L) the attack is network-reachable and requires no authentication, no user interaction and no special conditions beyond that reachability, and impact is confined to availability. Whether the RTR listener is affected through the identical mechanism is stated by the description at a high level; the precise code path and per-listener behaviour are not detailed in the available sources, and the vendor advisory referenced below should be consulted for the exact trigger and fix.
Know when Routinator gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Remote, low-complexity, unauthenticated connection exhaustion with no UI; no confidentiality or integrity impact and only partial (HTTP-server) availability loss, so A:L.
Primary rating from Vendor (NLnet Labs).
CVSS VectorVendor: NLnet Labs
DescriptionCVE.org
Routinator runs out of open connections on the HTTP server when many connections are opened but never closed, leaving the HTTP server unavailable. This condition can be triggered maliciously by an attacker by opening a large number of connections to the HTTP server.
This only affects users that make their HTTP or RTR server available to untrusted networks.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
More in Routinator
View allAn issue was discovered in NLnet Labs Routinator 0.1.0 through 0.7.1. Rated high severity (CVSS 7.4), this vulnerability
Denial of service in NLnet Labs Routinator allows remote attackers to crash the RPKI validator by serving a crafted Docu
Denial of service in NLnet Labs Routinator allows remote unauthenticated attackers to crash the daemon by opening a larg
Path traversal in NLnet Labs Routinator allows remote attackers to escape the rsync cache directory by supplying rsync U
Denial of service in NLnet Labs Routinator (an RPKI Relying Party software) allows remote attackers to crash the daemon
Routinator, NLnet Labs' RPKI relying party validator, mishandles RRDP notification files by accepting delta entries with
Routinator, NLnet Labs' RPKI relying-party validator, can be driven into memory exhaustion by an AS range in RPKI data w
Routinator exits when it encounters an RRDP-delivered rsync URI whose path cannot be stored on disk, producing a denial
Routinator, NLnet Labs' RPKI relying-party validator, can be hung or terminated by a CRL fetched from the repository hie
Due to a mistake in error checking, Routinator will terminate when an incoming RTR connection is reset by the peer too q
NLnet Labs' Routinator up to and including version 0.12.1 may crash when trying to parse certain malformed RPKI objects.
In NLnet Labs Routinator 0.9.0 up to and including 0.11.2, due to a mistake in error handling, data in RRDP snapshot and
EUVD-2026-110030
GHSA-qfwm-769m-74fg
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB