CVE-2024-49400: Meta Tacquito · Permissive Regular Expression
Affects Meta TacquitoSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 17 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Meta Tacquito | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2024-49400, organizations should: 1) Immediately identify all Tacquito deployments and verify their versions against the fixed commit 07b49d1358e6ec0b5aa482fcd284f509191119e2. 2) Apply official patches or updates from Meta as soon as they become available. 3) In the absence of patches, implement temporary controls such as restricting network access to Tacquito services and monitoring for anomalous command execution patterns. 4) Review and harden command authorization logic by enforcing strict full-string regex matching rather than substring matches. 5) Employ additional layers of access control and input validation to prevent unauthorized command injection. 6) Conduct thorough security audits and penetration tests focusing on command execution pathways. 7) Monitor logs and network traffic for suspicious activities indicative of exploitation attempts. 8) Educate system administrators and security teams about the vulnerability and recommended response actions. These steps go beyond generic advice by focusing on the specific regex matching flaw and command authorization mechanisms.
Description
Tacquito prior to commit 07b49d1358e6ec0b5aa482fcd284f509191119e2 was not properly performing regex matches on authorized commands and arguments. Configured allowed commands/arguments were intended to require a match on the entire string, but instead only enforced a match on a sub-string. That would have potentially allowed unauthorized commands to be executed.