Loading vulnerability…
CVE-2026-28912 is a privilege escalation vulnerability in Apple macOS caused by a logic issue. The flaw was addressed by introducing improved restrictions in macOS Sequoia 15.7.8 and macOS Tahoe 26.6. Available information indicates that the vulnerability allows a local user to bypass intended security checks or restrictions and gain elevated privileges, but specific details about the affected component or vulnerable function are not currently available.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This seven-file repository contains a standalone Bash proof of concept (poc.sh) and supporting Markdown reverse-engineering notes for CVE-2026-28912 in Apple PackageKit. The script creates $HOME/cve-poc/target as a symlink to $HOME/cve-poc/real, builds a .pkg with a payload path that traverses that symlink, and invokes sudo installer. Vulnerable PackageKit versions are reported to follow the directory symlink while moving the package payload, producing a root-owned poc.txt in the target directory rather than the declared destination. The documentation attributes the issue to PKCoreShove calling renamex_np without RENAME_NOFOLLOW_ANY in the normal installation case, and describes a Tahoe 26.6 upstream O_NOFOLLOW path-validation fix. There are no network operations, remote endpoints, reverse shells, or code-execution payloads. The PoC is intentionally benign by default, although the underlying primitive could be adapted to write attacker-selected content to privileged filesystem locations. One documentation inconsistency is present: README.md refers to link.sh and claims CONTENT can be supplied through the environment, while the actual entry point is poc.sh and it unconditionally assigns CONTENT="hello".
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.