Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach exposed HTTP/RTR server on untrusted network
-
ExploitOpen many concurrent JSON-output requests (or send oversized-metadata payload)
-
ExecutionExhaust memory or overflow stack
-
ImpactRoutinator process crashes/exits (RPKI validation 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 is limited to deployments that make the Routinator HTTP or RTR server available to untrusted networks - the vendor explicitly states only such users are affected, so operators who bind these services to localhost or trusted management segments are not exposed. Given that gate, no authentication or user interaction is required (PR:N/UI:N) and complexity is low: the OOM path needs only a high volume of concurrent JSON-output requests, and the stack-overflow path needs a payload item carrying excessive metadata that is discarded at once. The practical limiting factors are the non-default exposure of the server to untrusted networks and the vendor-assigned adjacent (AV:A) attack vector, which narrows reach versus a fully internet-wide attack unless the service is internet-facing. |
| Impact | This is a medium-severity availability-only flaw (vendor CVSS 6.5, CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) with no confidentiality or integrity impact - it is a denial-of-service, not a code-execution issue, despite the 'Buffer Overflow' tag. Two distinct defects exist: memory exhaustion (OOM) triggered by many concurrent JSON-output requests, and a stack overflow causing the process to exit when a payload item with excessive metadata is discarded. CWE-755 (improper handling of exceptional conditions) matches the availability-only, crash/exhaustion behaviour far better than a memory-corruption buffer overflow. Exploitation status is no public exploit identified at time of analysis - the input lists no KEV entry, no EPSS score, and no PoC reference (the single reference is the vendor advisory). The vuln.today decision label is 'this_month', indicating prioritized but non-emergency remediation. A key signal to verify: the vendor vector is AV:A (adjacent), yet the description frames the trigger as opening connections to an exposed HTTP/RTR server, which for internet-facing deployments would be a network (AV:N) condition - the real attack surface depends on where the operator binds these services. Net: a real but bounded priority, gated by the operator exposing the server to untrusted networks, with worst case being a crash/restart of the RPKI validator rather than data compromise. |
| Exploit ScenarioDerived | An attacker with reachability to a Routinator HTTP server exposed on an untrusted network opens a large number of concurrent connections repeatedly requesting the JSON output, driving the process out of memory. Alternatively, a crafted payload item carrying excessive metadata is discarded all at once, triggering a stack overflow that makes Routinator exit. No public exploit is identified at time of analysis; the attack requires no authentication (PR:N) and low complexity (AC:L). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 26, 2026
NLnet Labs Routinator, an RPKI relying party validator, can be driven into memory exhaustion by a flood of concurrent requests to its HTTP JSON output endpoint, and can also abort with a stack overflow when a payload item carrying excessive metadata is discarded in a single operation. Only deployments that expose the HTTP or RTR server to untrusted networks are affected; the flaw is availability-only (no confidentiality or integrity impact), requires no authentication or user interaction, and no public exploit code was identified at the time of analysis. Vendor severity is 6.5 (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), while the independent assessment rates the attack vector as network (AV:N) rather than adjacent, and the priority decision is this_month.
RemediationAI
The supplied intelligence does not specify a fixed release version, so treat the vendor advisory at https://www.nlnetlabs.nl/downloads/routinator/CVE-2026-72752.txt as the source of truth for the patched Routinator version and upgrade to it as soon as it is confirmed for your branch; until then, apply the exposure restriction the vendor names as the determining factor. Concretely, bind the HTTP and RTR listeners to loopback or a management interface, or firewall the HTTP JSON endpoint and the RTR port so that only known RTR clients and monitoring systems can reach them - the trade-off is that remote consumers, dashboards and downstream RTR caches stop working until they are moved behind the allowed segment or a proxy. As an additional cushion against the out-of-memory path, place a reverse proxy in front of the HTTP JSON endpoint that caps concurrent requests and connection counts and set process-level memory limits with automatic restart so a successful flood degrades to a restart rather than a host-level OOM; the trade-off is added latency, truncated responses under load, and brief RTR resets on restart. Monitor Routinator memory usage and exit events for evidence of either failure mode.
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 a Rust-based RPKI relying party validator that fetches and validates RPKI repository data, produces Validated ROA Payloads, and publishes them to other software through an HTTP interface (including JSON output) and an RTR protocol server. The weakness is classified as CWE-755, Improper Handling of Exceptional Conditions: the service does not bound the resources consumed by concurrent serialization work or by the disposal of unusually large payload metadata, so error/edge-case handling paths turn into resource-exhaustion paths. The CPE entry cpe:2.3:a:nlnet_labs:routinator:*:*:*:*:*:*:*:* uses a wildcard version, so the provided intelligence does not pin a specific affected release range; operators must confirm their build against the vendor advisory. Two distinct failure modes are described: out-of-memory conditions under a high volume of simultaneous JSON output requests, and a stack overflow leading to process exit when a payload item with an excessive amount of metadata is discarded at once. The exact code path that triggers the stack overflow is not described in the available sources.
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:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Reachable HTTP/RTR server abused by unauthenticated low-complexity requests for availability-only impact; I assess AV:N for internet-facing exposure though the vendor chose AV:A (adjacent).
Primary rating from Vendor (NLnet Labs).
CVSS VectorVendor: NLnet Labs
DescriptionCVE.org
Routinator runs out of memory when the JSON output is requested many times concurrently. This condition can be triggered maliciously by an attacker by opening a large number of connections to the HTTP server. Additionally Routinator runs into a stack overflow and exits when a payload item with too much metadata is discarded at once.
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
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
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-110025
GHSA-9hhm-hxh6-hwxr
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB