What is CVE-2026-49428?

CVE-2026-49428 is posixshm: system calls can incorrectly free memory of largepage objects. The supplied enrichment data classifies it as Remote Code Exec mapped to CWE-915 CWE-915.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-49428. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-49428 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

A public PoC is not confirmed from current sources for CVE-2026-49428. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with EDR process telemetry, host service logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-49428 using CVSS null, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

Remote Code Exec

CVE-2026-49428

CVE-2026-49428 — posixshm: system calls can incorrectly free memory of largepage objects

Certain system calls, such open(2) with the O_TRUNC flag set, and fspacectl(2), could incorrectly free memory in largepage objects. These operations are not permitted on largepage objects, but the implementation did not verify this. An unprivileged local user can abuse the bug to access freed kernel memory. This can be exploited to escalate privileges.

Published Aug 19, 2026Updated Aug 19, 2026Sources: NVD, FreeBSD (CNA), GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

ahead of 0% of scored CVEs

Affects

FreeBSD

4 products listed

CVSS base

Unscored

no source published a base score

Remediation

The vendor's own words where we have them.

Upgrade FreeBSD to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
FreeBSD	FreeBSD	15.1-RELEASE	Vulnerable
FreeBSD	FreeBSD	15.0-RELEASE	Vulnerable
FreeBSD	FreeBSD	14.4-RELEASE	Vulnerable
FreeBSD	FreeBSD	14.3-RELEASE	Vulnerable

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-915 · Improperly Controlled Modification of Dynamically-Determined Object Attributes

Modify Application Data
Execute Unauthorized Code or Commands
Varies by Context
Alter Execution Logic::

Mitigation: If available, use features of the language or framework that allow specification of allowlists of attributes or fields that are allowed to be modified. If possible, prefer allowlists over denylists. For applications written with Ruby on Rails, use the attr_accessible (allowlist) or attr_protected (denylist) macros in each class that may be used in mass assignment.

Weakness & attack patterns

CWE-915

Inferred from the weakness class — not observed against this CVE.

CAPEC-242 · Code InjectionCAPEC-35 · Leverage Executable Code in Non-Executable Files

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

EDR process telemetryhost service logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Initial · CVE published
Aug 19, 2026 · NVD

Source activity

Readings a source repeats on a schedule, counted rather than listed.

1×CVE modified by NIST, Modified, LinkAug 19, 2026 · SOCRadar CTI

References

1 on the record

security.freebsd.org/advisories/FreeBSD-SA-26:44.posixshm.asc
Vendor Advisory

Elsewhere on this site

FreeBSDevery CVE for this vendor
Remote Code Execsame class
CWE-915other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-49428 is posixshm: system calls can incorrectly free memory of largepage objects, a unscored vulnerability affecting FreeBSD from FreeBSD. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-49428. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-49428. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS null describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.