How severe is GHSA-33mj-99mg-8g73?

No CVSS score has been assigned to GHSA-33mj-99mg-8g73 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-33mj-99mg-8g73?

GHSA-33mj-99mg-8g73 affects the following packages: routinator (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-33mj-99mg-8g73?

Update routinator to 0.15.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-33mj-99mg-8g73 is resolved across your whole dependency graph.

How do I detect GHSA-33mj-99mg-8g73 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for routinator, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-33mj-99mg-8g73 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is GHSA-33mj-99mg-8g73 actively exploited in the wild?

No public exploit code has been indexed for GHSA-33mj-99mg-8g73 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-33mj-99mg-8g73?

GHSA-33mj-99mg-8g73 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 41th 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-33mj-99mg-8g73?

GHSA-33mj-99mg-8g73 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-33mj-99mg-8g73 published, and has it been updated?

GHSA-33mj-99mg-8g73 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-33mj-99mg-8g73 — routinator

GHSA-33mj-99mg-8g73 is a Path Traversal vulnerability in routinator. A fix is available for routinator — see the affected versions and patch details below.

Routinator has cache path traversal when processing the module component of rsync URIs

Also known asCVE-2026-49233

Published

Jun 8, 2026

Updated

Jun 12, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
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-33mj-99mg-8g73.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs41th percentile — riskier than 41% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

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

Routinator does not properly check the module component of rsync URIs, which are used to create the file system paths for the Routinator cache. This allows for path traversal by having a module name containing .., potentially providing an attacker access to the entire Routinator rsync cache.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`routinator`	all versions	0.15.2`cargo update -p routinator --precise 0.15.2`

Affected Products

1 product · 1 configurations

Application

routinatornlnetlabs

< 0.15.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for routinator, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update routinator to 0.15.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-33mj-99mg-8g73 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-33mj-99mg-8g73 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works