How severe is GHSA-5qf9-cf9c-hjc6?

No CVSS score has been assigned to GHSA-5qf9-cf9c-hjc6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-5qf9-cf9c-hjc6?

GHSA-5qf9-cf9c-hjc6 affects the following packages: routinator (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-5qf9-cf9c-hjc6?

Update routinator to 0.15.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5qf9-cf9c-hjc6 is resolved across your whole dependency graph.

How do I detect GHSA-5qf9-cf9c-hjc6 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for routinator. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-5qf9-cf9c-hjc6 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-5qf9-cf9c-hjc6?

O3 pinpoints whether GHSA-5qf9-cf9c-hjc6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-5qf9-cf9c-hjc6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-5qf9-cf9c-hjc6 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-5qf9-cf9c-hjc6?

GHSA-5qf9-cf9c-hjc6 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 29th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-5qf9-cf9c-hjc6?

GHSA-5qf9-cf9c-hjc6 is classified as CWE-755 (CWE-755). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-5qf9-cf9c-hjc6 published, and has it been updated?

GHSA-5qf9-cf9c-hjc6 was published on June 8, 2026 and was last updated on June 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

GHSA-5qf9-cf9c-hjc6

GHSA-5qf9-cf9c-hjc6 is a CWE-755 vulnerability in routinator. O3 Security confirms whether GHSA-5qf9-cf9c-hjc6 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Routinator crashes when encountering maliciously crafted RRDP XML files

Also known asCVE-2026-49235

Published

Jun 8, 2026

Updated

Jun 12, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-5qf9-cf9c-hjc6.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs29th percentile — riskier than 29% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

🦀routinator

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

When Routinator encounters a file via RRDP using a specifically crafted Document Type Definition, Routinator crashes.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`routinator`	all versions	0.15.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for routinator. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update routinator to 0.15.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5qf9-cf9c-hjc6 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-5qf9-cf9c-hjc6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-5qf9-cf9c-hjc6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

When Routinator encounters a file via RRDP using a specifically crafted Document Type Definition, Routinator crashes.

O3 Security · Impact-Aware SCA

Is GHSA-5qf9-cf9c-hjc6 in your dependencies?

O3 detects GHSA-5qf9-cf9c-hjc6 across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works