Permissive Regular Expression in tacquito

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

7.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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

Published by the source

18 Oct 2024, 18:40 UTC

Last modified by the source

1 Nov 2024, 21:47 UTC

Source last checked

26 Oct 2026, 15:05 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-p5wf-cmr4-xrwr

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-p5wf-cmr4-xrwr

Advisory: Permissive Regular Expression in tacquito
IDs: GHSA-p5wf-cmr4-xrwr
Record: https://patchnext.com/advisories/ghsa-p5wf-cmr4-xrwr (revision 1, source checked 26 Oct 2026, 15:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/facebookincubator/tacquito 0.0.0-20241011192817-07b49d1358e6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/facebookincubator/tacquito: affected < 0.0.0-20241011192817-07b49d1358e6; fixed in 0.0.0-20241011192817-07b49d1358e6

## Suggested inspection (read-only)
- Go github.com/facebookincubator/tacquito: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/facebookincubator/tacquito.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-p5wf-cmr4-xrwr (GitHub-reviewed advisory GHSA-p5wf-cmr4-xrwr lists affected ranges: Go github.com/facebookincubator/tacquito >=0 <0.0.0-20241011192817-07b49d1358e6)

Commands are suggestions: review each one before running it.