Skip to main content
Mallory
UnratedPublic exploitVulnerability

CVE-2026-112445

Updated 18 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days5 mentions · peak 3 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2026-112445
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
CVE-2026-112445The supplied repository contains README.md (2,897 bytes) and exp.c (4,040 bytes), a standalone C local privilege-escalation implementation with a hardcoded payload. The README describes a root Bash launchd job whose standard streams connect to /dev/console, allegedly allowing the active non-administrator console user to supply commands through TIOCSTI. The executable copies itself into a randomized temporary directory. A forked child establishes a new session, acquires /dev/console as its controlling terminal, and injects a command character by character after a four-second delay. The parent invokes launchctl kickstart for system/com.apple.xpc.uscwoap. The injected command makes the copied executable root-owned and mode 4755. After checking the helper's ownership and permissions, the parent executes it with --shell; this branch sets UID/GID to zero and opens an interactive privileged Bash shell. Normal cleanup deletes the helper and its directory, although abnormal termination can leave artifacts. This is exploitation code rather than a detection-only script. It contains no network communications, remote callback, or exploit-framework integration. Its success depends on launchd authorization, console ownership and terminal ioctl behavior, as well as timing and setuid support. The README attributes the issue to CVE-2026-112445 and claims macOS 27.2 removes the job; neither the identifier, affected release range, nor remediation claim is independently verified by the supplied material. Repository URL, git reference, and archive size were not provided; empty strings and zero represent unavailable metadata.Mas0nShi · Disclosed Oct 29, 2026 · c · localOperational
FAQ

Frequently asked questions

Is CVE-2026-112445 exploited in the wild?
As of Nov 4, 2026, Mallory has no reports of CVE-2026-112445 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-112445?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-112445, the earliest disclosed Oct 29, 2026.
Activity feed

Recent activity

5 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity5Community discussion across Reddit, Mastodon, and other social sources.