GHSA-p5wf-cmr4-xrwr is a high-severity (CVSS 7.6) vulnerability in github.com/facebookincubator/tacquito. A fix is available for github.com/facebookincubator/tacquito — see the affected versions and patch details below.
Permissive Regular Expression in tacquito
Real-World Exposure
github.com/facebookincubator/tacquitoReal-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
Impact
The CVE is for a software vulnerability. Network admins who have deployed tacquito (or versions of tacquito) in their production environments and use tacquito to perform command authorization for network devices should be impacted.
Tacquito code prior to commit 07b49d1358e6ec0b5aa482fcd284f509191119e2 was performing regex matches on authorized commands and arguments in a more permissive than intended manner. Configured allowed commands/arguments were intended to require a match on the entire string, but instead only enforced a match on a sub-string. This behaviour could potentially allowed unauthorized commands to be executed.
Patches
The problem has been patched, and users should update to the latest github repo commit to get the patch.
Workarounds
Users should be able to add boundary conditions anchors '^' and '$' to their command configs to remediate the vulnerability without the upgrade
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/facebookincubator/tacquito | all versions | 0.0.0-20241011192817-07b49d1358e6go get github.com/facebookincubator/tacquito@v0.0.0-20241011192817-07b49d1358e6 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/facebookincubator/tacquito, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/facebookincubator/tacquito to 0.0.0-20241011192817-07b49d1358e6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p5wf-cmr4-xrwr 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-p5wf-cmr4-xrwr can be triaged on real exposure rather than presence alone.
Tailored to GHSA-p5wf-cmr4-xrwr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-p5wf-cmr4-xrwr in your dependencies?
O3 Security finds GHSA-p5wf-cmr4-xrwr across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.