CVE-2026-122137 Powerlevel10k before 1.20.19 Insecure Temporary Directory via gitstatus Installer
Medium 5.4
Published
Updated
Check this codebase for CVE-2026-122137 and fix it if it is affected.
What it is: CVE-2026-122137 is a medium-severity vulnerability in romkatv gitstatus, published on 4 Nov 2026.
Exploitation: There is no known exploitation of CVE-2026-122137 in the wild and no public exploit code.
Affected product: romkatv gitstatus. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-122137/ (Markdown: https://insights.sbomify.com/CVE-2026-122137/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-122137?
CVE-2026-122137 is a medium-severity vulnerability in romkatv gitstatus, published on 4 Nov 2026.
Official description
Powerlevel10k before 1.20.19 contains an insecure temporary directory vulnerability in the bundled gitstatus/install script that reuses attacker-creatable directories when mktemp fails. Local attackers can pre-create the predictable gitstatus-install.tmp directory to replace the extracted gitstatusd binary, which then executes with the victim's privileges.
Weakness: CWE-377
Which versions are affected by CVE-2026-122137?
How do I fix CVE-2026-122137?
No fix has been published for CVE-2026-122137 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-122137 being exploited?
There is no known exploitation of CVE-2026-122137 in the wild and no public exploit code.
Sources
Also known as GHSA-pfwr-f3c5-mfgm.