EUVD-2026-33751
GHSA-8v4r-w49g-jc9w
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconGain local account on build host
-
DeliveryPredict /tmp notarization paths
-
ExploitPre-create symlink or poll for key file
-
InstallWorkflow writes API key and ZIP to predictable path
-
C2Read App Store Connect key or redirect archive write
-
ExecuteSubstitute tampered notarization archive
-
ImpactAbuse stolen key or ship trojanized signed build
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Secure temp file creation
|
| Exploitation Conditions | Attacker must already have an interactive local account or code-execution foothold on the same macOS host where CodexBar's release notarization workflow runs (CVSS AV:L, PR:L), and must be able to observe or write to the fixed shared /tmp paths used for the App Store Connect API key file and the notarization upload ZIP before or during a release run - the AT:P bit in the CVSS 4.0 vector reflects this timing/pre-creation requirement. Exploitation is limited to hosts where the maintainer actually executes the CodexBar release/notarization workflow (typically a developer's or CI build machine, not end-user installations of the app), and is gated by the attacker's ability to win a race or have a symlink in place when the workflow runs; it does not work remotely and does not affect users who only run the prebuilt CodexBar binary. |
| Impact | The CVSS 4.0 vector AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N reflects a local, low-complexity attack requiring some attack precondition (AT:P - racing or pre-creating the predictable path) and low privileges, with high confidentiality and integrity impact but no availability impact. There is no EPSS score, KEV listing, or public POC referenced, so real-world risk is bounded by the local attacker model: realistic exposure is multi-user macOS build hosts or CI runners where another account or process can observe /tmp during a release run. For typical single-developer macOS desktops the practical risk is low, but for shared signing/notarization infrastructure the impact (theft of an Apple App Store Connect key and substitution of a notarized artifact) is severe and would enable downstream supply-chain abuse. AT:P combined with PR:L indicates this is not a remote, easily automatable issue - it should be prioritized based on whether the host is multi-tenant or hosts release tooling, not solely on the 7.2 base score. |
| Exploit ScenarioDerived | On a shared macOS build host, an unprivileged local user enumerates the well-known /tmp path used by CodexBar's notarization workflow and either reads the App Store Connect API key file the moment it is written or pre-creates a symlink so the workflow's ZIP write is redirected to an attacker-controlled location, where the attacker swaps in a malicious notarization archive. The attacker then either reuses the stolen Apple API key to sign their own artifacts or lets CodexBar submit the tampered archive to Apple under the legitimate developer identity. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv3 – Jun 01, 2026
Local privilege-level information disclosure and artifact tampering in CodexBar versions prior to 0.32.0 allows authenticated users on the same macOS host to read App Store Connect API keys and hijack release builds via predictable temporary file paths in the notarization workflow. The flaw stems from writing sensitive credentials and notarization archives to fixed, world-reachable locations rather than per-run private directories, enabling symlink races and pre-creation attacks. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV.
Earlier versions of this analysis (2)
Local privilege abuse in CodexBar prior to 0.32.0 lets co-resident users on macOS hosts steal App Store Connect API keys and hijack the release notarization pipeline by exploiting predictable temporary file paths under /tmp. The CWE-377 weakness enables symlink redirection of writes, theft of signing credentials, and tampering with notarization archives before they are submitted to Apple. No public exploit identified at time of analysis, but the vendor has shipped a fix and the issue was disclosed via VulnCheck.
Local privilege-scoped information disclosure and write redirection in CodexBar (macOS menu-bar utility by steipete) prior to 0.32.0 lets a same-host attacker steal App Store Connect API keys and tamper with notarization archives by abusing predictable temporary file paths used during the release notarization workflow. No public exploit identified at time of analysis, but the patch and an accompanying VulnCheck advisory describe the predictable-path mechanism in detail.
RemediationAI
Vendor-released patch: upgrade CodexBar to 0.32.0 or later, which isolates notarization API keys and upload ZIPs in a private per-run temporary directory rather than predictable shared /tmp paths (see https://github.com/steipete/CodexBar/releases/tag/v0.32.0 and commit https://github.com/steipete/CodexBar/commit/e7d932616508cee43ea9bcc63c269b14698de655). If immediate upgrade is not possible, run release/notarization only on single-user macOS hosts and avoid shared build agents, set restrictive umask (077) for the release user and pre-create a private mkdtemp-style staging directory owned solely by that user, and rotate any App Store Connect API key that may have been written to a predictable path during prior runs (rotation invalidates any previously stolen key but requires re-distributing the new key to legitimate signers).
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CodexBar is a macOS menu bar utility (cpe:2.3:a:steipete:codexbar) that provides dashboards and status for AI coding providers such as Codex, Claude, and Antigravity. The vulnerable component is its release/notarization tooling, which historically staged the Apple App Store Connect API key and the ZIP archives submitted to Apple's notarization service in a shared, predictable directory (effectively a fixed path under /tmp). CWE-377 (Insecure Temporary File) captures the root cause: a temporary file is created in a location an attacker can predict and racily pre-populate with a regular file or symlink before the privileged writer touches it, breaking the implicit confidentiality and integrity assumptions of the workflow.
Know when Codexbar gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Primary rating from Vendor (VulnCheck) · only source for this CVE.
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
3DescriptionCVE.org
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.
Executive ViewAI
CodexBar versions before 0.32.0 allow other authenticated users on the same development machine to steal App Store Connect credentials and tamper with software builds, with no public exploit identified at time of analysis. Development teams using vulnerable versions face material risk of compromised app releases and credential theft. Patch is available and should be deployed immediately.
Apply vendor patch.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Cleartext session cookie exposure in CodexBar (a macOS menu bar AI provider client) prior to 0.32.0 allows network-posit
Local privilege escalation in CodexBar prior to 0.32.0 allows a same-user attacker to execute arbitrary commands as root
Credential interception in CodexBar before 0.33.0 exposes API keys, bearer tokens, and browser cookies to network-adjace
Exploit-DB