CVE-2026-88937 is a high severity path traversal flaw in knowns, scored 8.8. The record does not name a fixed version. Check your installed version against the affected list below, then patch or restrict access until you can. The record does not flag it as exploited.
What's affected
- knowns through 0.33.0.
Severity in the record: High (8.8), vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Weakness: CWE-22.
Fix: The record does not name a fixed version. Check the GitHub advisories GHSA-68cq-4rwm-f7jr and GHSA-xjcg-5j3r-m6f9.
How to check if you're exposed
- Check the installed version against 0.33.0 using your install method, for example the tool's version command or your package manifest.
- Review any templates you have loaded from third parties.
Run these on every host, image and build that could carry the component. Dependency files in repositories and base images in registries are easy to miss.
What to do now
- Confirm the version of every affected system using the checks above.
- Read the vendor advisory linked in Sources and note the fixed version for your release line.
- Schedule the update, starting with systems that face untrusted networks or hold the most sensitive data.
- In the meantime: use only templates you wrote or reviewed.
- Record the change, then recheck the version to confirm it took effect.
Why it matters
The code generation template engine does not properly validate destination paths, so templates can read and write files outside the project root (CWE-22). The record says a malicious template could overwrite shell profiles or steal credentials. The vector has user interaction required, which fits using a template someone else supplied. Treat templates like code.
The record's KEV flag is false, so this post makes no claim that the flaw is exploited in the wild. That can change, so recheck the CISA catalog from time to time.
Libraries like this often arrive as transitive dependencies, so the version in your lockfile may not be one you chose. Safeguard's free in-browser dependency scan can show whether the package is in a project, and reachability analysis helps separate code paths that call the weak function from those that never do.
The vector string in the record is a compact summary of how the flaw is reached and what it costs. AV is the attack vector (network, adjacent or local), PR is the privilege the attacker needs, and the C, I and A letters give the impact on confidentiality, integrity and availability. Read it against your own network layout rather than relying on the score alone.
After you patch
Patching is not the end of the job. Recheck the version on each system, because an upgrade that failed or rolled back looks the same as a success until someone looks. Keep the advisory link with your change record so the next reviewer can see why the update happened.
If you cannot patch soon, write down the reason, the compensating control you chose and a date to revisit. Exceptions without a date tend to become permanent.
Quick check
Why is user interaction required?
The victim has to use an attacker-supplied template.
Sources
-
GitHub: GHSA-68cq-4rwm-f7jr
-
Safeguard Gold: CVE-2026-88937
Last reviewed: 18 October 2026.
