CVE-2026-49135: steipete CodexBar · Insecure Temporary File
Affects steipete CodexBarSource CVE Database V5
Not known to be exploited · CVSS 7.2 High : upgrade to 0.32.0 soon.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.32.0
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 1 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 Oct 2026.
What to do
Upgrade steipete/CodexBar and CodexBar to 0.32.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| steipeteCodexBar | Affected
| Fixed in– |
GitHubsteipete/CodexBarpkg:github/steipete/CodexBarOther threats | Affected
| Fixed in
|
GitHubCodexBarpkg:github/CodexBarOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, avoid running CodexBar in multi-user environments where untrusted users have local access. Restrict file system permissions to prevent unauthorized creation or modification of files in predictable temporary file locations used by CodexBar.
Description
CodexBar prior to 0.32.0 contains an insecure temporary file handling vulnerability that allows local attackers to access sensitive credentials or tamper with build artifacts by exploiting predictable file paths in the release notarization workflow. Attackers with access to the same host can read the App Store Connect API key written to a fixed path, pre-create files or symbolic links at predictable locations to redirect writes to attacker-controlled destinations, or tamper with notarization archives before submission.
References
- github.com/steipete/CodexBar/releases/tag/v0.32.0 (opens in a new tab)
- github.com/steipete/CodexBar/pull/1228 (opens in a new tab)
- github.com/steipete/CodexBar/commit/e7d932616508cee43ea9bcc63c269b14698de655 (opens in a new tab)
- vulncheck.com/advisories/codexbar-insecure-temporary-file-handling-in-notarization-workflow (opens in a new tab)