Skip to main content
Mallory
HighVulnerability

CVE-2026-57589: OpenBSD System V Semaphore sys_semget() Use-After-Free Privilege Escalation

Published Jun 25, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS0.17%6th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Openbsd
IdentifiersCVE-2026-57589CWE-416 · Use After Free

CVE-2026-57589 is a local privilege-escalation vulnerability in OpenBSD's System V semaphore implementation, affecting releases through OpenBSD 7.9. The primary vulnerability description identifies a use-after-free in sys/kern/sysv_sem.c: a context switch following tsleep in sys_semget() can leave freed memory accessible. Exploitation may enable a local attacker to obtain root privileges. Separate accounts characterize the underlying flaw as an integer overflow in sys_semget() causing kernel memory corruption; this characterization conflicts with the use-after-free classification.

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

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A local attacker may exploit the flaw to escalate privileges to root. The reported integer-overflow characterization additionally states that exploitation can cause kernel memory corruption.

Mitigation

If you can’t patch tonight, do this now.

Restrict local shell and account access to trusted users until patched systems can be deployed. Minimize exposure by disabling or avoiding untrusted local multi-user access paths such as shared shell environments, developer jump hosts, and similar scenarios where unprivileged users can execute code locally. Where operationally feasible, reduce reliance on System V semaphore functionality until the fix is applied.

Remediation

Patch, then assume compromise.

Upgrade to an OpenBSD release newer than 7.9 once a vendor fix is available. A fix was committed to the OpenBSD-current branch on June 23; stable-branch fixes were reported as pending at the time of reporting.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
OpenbsdOpenbsdoperating_system
FAQ

Frequently asked questions

Is CVE-2026-57589 exploited in the wild?
As of Sep 30, 2026, Mallory has no reports of CVE-2026-57589 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-57589?
As of Sep 30, 2026, Mallory has found no public exploit for CVE-2026-57589.
Is there a patch for CVE-2026-57589?
Upgrade to an OpenBSD release newer than 7.9 once a vendor fix is available. A fix was committed to the OpenBSD-current branch on June 23; stable-branch fixes were reported as pending at the time of reporting.
What products are affected by CVE-2026-57589?
Openbsd.
How severe is CVE-2026-57589?
CVE-2026-57589 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 0.17% (6th percentile) as of Sep 30, 2026.
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 activity31Community discussion across Reddit, Mastodon, and other social sources.