CVE-2026-49235
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWhen Routinator encounters a file via RRDP using a specifically crafted Document Type Definition, Routinator crashes.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceRoutinator, an RPKI validator, crashes when processing a maliciously crafted XML Document Type Definition (DTD) received via the RPKI Repository Delta Protocol (RRDP). This is a denial-of-service vulnerability triggered by specially crafted RRDP content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.15.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Routinator is installedCheck for the routinator process running (e.g., `ps aux | grep routinator`) or locate the binary (e.g., `which routinator` or check common installation paths like /usr/bin/routinator)Affected if Routinator process or binary is found on the system
-
Determine installed versionRun `routinator --version` to obtain the exact version number, then compare it to the affected range (versions prior to 0.15.2)Affected if Version is lower than 0.15.2 (for example, 0.15.1, 0.14.x, etc.)
-
Confirm RRDP is enabledInspect the Routinator configuration file (typically at /etc/routinator/routinator.conf or ~/.routinator.conf) and look for the rrdp section; check if 'enabled' is set to true or if RRDP is listed as a trust anchor update methodAffected if RRDP is enabled in the configuration and used for RPKI data retrieval
-
Check for crash logsReview system logs (journalctl, syslog, or /var/log/messages) and Routinator logs for recent crashes, assertion failures, or unexpected termination events matching the timeframe of RRDP updatesAffected if Logs show sudden crashes or process termination with RRDP-related error messages
If Routinator version is below 0.15.2 and RRDP is enabled for RPKI data fetching, the environment is vulnerable to this denial-of-service flaw.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.15.2
Disable RRDP support in Routinator configuration until a patched version is available from the vendor. Monitor for updates from NLnet Labs.
Routinator 0.15.2
- Check current Routinator version: routinator --version
- Stop the Routinator service if running
- Download Routinator version 0.15.2 from the official NLnet Labs repository or releases page
- Install the updated version using your system's package manager or by replacing the binary
- Restart the Routinator service
- Verify the upgrade was successful by checking: routinator --version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49235 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-49235 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data