CVE-2019-25073 is a high-severity (CVSS 7.5) Path Traversal vulnerability in github.com/goadesign/goa. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for github.com/goadesign/goa — see the affected versions and patch details below.
Goa vulnerable to path traversal
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 CVE-2019-25073.
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
github.com/goadesign/goa🐹goa.design/goa🐹goa.design/goa/v3Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Improper path sanitization in github.com/goadesign/goa before v3.0.9, v2.0.10, or v1.4.3 allow remote attackers to read files outside of the intended directory.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/goadesign/goa | all versions | 1.4.3go get github.com/goadesign/goa@v1.4.3 |
| 🐹Go | goa.design/goa | all versions | 1.4.3go get goa.design/goa@v1.4.3 |
| 🐹Go | goa.design/goa/v3 | all versions | 3.0.9go get goa.design/goa/v3@v3.0.9 |
Affected Products
goagoa.designResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/goadesign/goa, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/goadesign/goa to 1.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-25073 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
Is CVE-2019-25073 in your dependencies?
Find it across Go, including transitive dependencies.