{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-121577 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-121577 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-121577 is a medium-severity vulnerability in lucasrodes whatstk, published on 3 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-121577 and fix it if it is affected.\n\nWhat it is: CVE-2026-121577 is a medium-severity vulnerability in lucasrodes whatstk, published on 3 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-121577 in the wild and no public exploit code.\n\nAffected product: lucasrodes whatstk. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-121577/ (Markdown: https://insights.sbomify.com/CVE-2026-121577/index.md)","id":"CVE-2026-121577","markdown":"https://insights.sbomify.com/CVE-2026-121577/index.md","name":"CVE-2026-121577","record":{"aliases":["GHSA-g94x-jrvx-m3cv"],"analysis":null,"analysis_generated_by":null,"assigner":"Secur0","cpe":[],"cvss":{"score":6.7,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-1333","name":"Inefficient Regular Expression Complexity"}],"description":"Inefficient Regular Expression Complexity (CWE-1333) in generate_regex() (whatstk/whatsapp/parser.py) in whatstk from 0.2.0 before 0.9.0 allows a party that supplies a chat export to consume the CPU of the process that parses it for an unbounded time, because the function builds the header regular expression by replacing each %x code with its named capture group and leaves every other character of the header format in the pattern unescaped. A header whose date separator is a regular expression metacharacter therefore alters the pattern instead of matching itself: a separator of + quantifies the preceding capture group, giving (?P\u003cday\u003e\\d{1,2})+(?P\u003cmonth\u003e\\d{1,2})+(?P\u003cyear\u003e\\d{2,4}), and a run of digits that cannot complete the header then makes the engine try every way of partitioning that run. Header auto detection is enabled by default and derives the format from the text of the file, so the separator is taken from the export itself and no header format has to be passed by the caller. Separators of (, ) and \\ instead raise re.PatternError, separators of *, | and ? raise TypeError, and separators of ^ and $ raise KeyError, none of which the library catches. This results in the parse of a file of a few hundred bytes consuming CPU without completing, or in an uncaught exception in the calling program.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Unescaped header separators in whatstk build a regular expression that backtracks exponentially","id":"CVE-2026-121577","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"CVE-2026-121578","id":"CVE-2026-121578"},"nickname":null,"packages":[],"prev":{"headline":"WordPress MCP Server for WordPress plugin \u003c= 2.0.1 - Privilege Escalation vulnerability","id":"CVE-2026-121576"},"products":["whatstk"],"published":"2026-11-03","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-11-06","vendors":["lucasrodes"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-121577/"}