Skip to main content
VulnerabilityPublished Updated

CVE-2026-49135: steipete CodexBar · Insecure Temporary File

Affects steipete CodexBarSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.2 High : upgrade to 0.32.0 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
steipeteCodexBarAffected
  • <0.32.0
Fixed in–
GitHubsteipete/CodexBarpkg:github/steipete/CodexBarOther threatsAffected
  • <0.32.0
Fixed in
  • 0.32.0
GitHubCodexBarpkg:github/CodexBarOther threatsAffected
  • <0.32.0
Fixed in
  • 0.32.0

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

Community reviews

Loading reviews…