CVE-2025-46096 is a medium-severity (CVSS 6.1) Path Traversal vulnerability in org.noear:solon-faas-luffy. A fix is available for org.noear:solon-faas-luffy — see the affected versions and patch details below.
Solon Vulnerable to Directory Traversal
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-46096.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.noear:solon-faas-luffyReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Directory Traversal vulnerability in solon v.3.1.2 allows a remote attacker to conduct XSS attacks via the solon-faas-luffy component
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.noear:solon-faas-luffy | ≥ 3.1.2&&< 3.2.0 | 3.2.0org.noear:solon-faas-luffy:3.2.0 |
Affected Products
solonnoearDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.noear:solon-faas-luffy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.noear:solon-faas-luffy to 3.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-46096 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2025-46096 in your dependencies?
Find it across Maven, including transitive dependencies.