Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2026-29111: systemd: Local unprivileged user can trigger an assert

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: azl3 systemd-bootstrap 250.3-19 on Azure Linux 3.0 250.3-19; cbl2 systemd-bootstrap 250.3-13 on CBL Mariner 2.0 250.3-14; cbl2 systemd-bootstrap 250.3-14 on CBL Mariner 2.0 250.3-14.

Low priority for now. Upgrade to azl3 systemd-bootstrap 250.3-19 on Azure Linux 3.0 250.3-19; cbl2 systemd-bootstrap 250.3-13 on CBL Mariner 2.0 250.3-14; cbl2 systemd-bootstrap 250.3-14 on CBL Mariner 2.0 250.3-14 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

systemd, a system and service manager, (as PID 1) hits an assert and freezes execution when an unprivileged IPC API call is made with spurious data. On version v249 and older the effect is not an assert, but stack overwriting, with the attacker controlled content. From version v250 and newer this is not possible as the safety check causes an assert instead. This IPC call was added in v239, so versions older than that are not affected. Versions 260-rc1, 259.2, 258.5, and 257.11 contain patches. No known workarounds are available.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Mar 23, 2026
Updated
Jun 17, 2026
EPSS
0.1% · 2th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
5.5
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-29111

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for systemd project records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
systemd projectsystemd

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • systemd project systemd239 and later · before 257.11
  • systemd project systemd258 and later · before 258.5
  • systemd project systemd259 and later · before 259.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • systemd systemd

    • >= 239, < 257.11, >= 258, < 258.5, >= 259, < 259.2affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10systemdbefore 257-23.el10_2.1.alma.1257-23.el10_2.1.alma.1
AlmaLinux:10systemd-boot-unsignedbefore 257-23.el10_2.1.alma.1257-23.el10_2.1.alma.1
AlmaLinux:10systemd-containerbefore 257-23.el10_2.1.alma.1257-23.el10_2.1.alma.1
AlmaLinux:10systemd-develbefore 257-23.el10_2.1.alma.1257-23.el10_2.1.alma.1
AlmaLinux:10systemd-journal-remotebefore 257-23.el10_2.1.alma.1257-23.el10_2.1.alma.1
AlmaLinux:10systemd-libsbefore 257-23.el10_2.1.alma.1257-23.el10_2.1.alma.1
AlmaLinux:10systemd-oomdbefore 257-23.el10_2.1.alma.1257-23.el10_2.1.alma.1
AlmaLinux:10systemd-pambefore 257-23.el10_2.1.alma.1257-23.el10_2.1.alma.1
AlmaLinux:10systemd-resolvedbefore 257-23.el10_2.1.alma.1257-23.el10_2.1.alma.1
AlmaLinux:10systemd-rpm-macrosbefore 257-13.el10_1.3.alma.1257-13.el10_1.3.alma.1
AlmaLinux:10systemd-rpm-macrosbefore 257-23.el10_2.1.alma.1257-23.el10_2.1.alma.1
AlmaLinux:10systemd-udevbefore 257-23.el10_2.1.alma.1257-23.el10_2.1.alma.1
AlmaLinux:10systemd-ukifybefore 257-13.el10_1.3.alma.1257-13.el10_1.3.alma.1
AlmaLinux:10systemd-ukifybefore 257-23.el10_2.1.alma.1257-23.el10_2.1.alma.1
AlmaLinux:9rhel-net-naming-sysattrsbefore 252-55.el9_7.9.alma.1252-55.el9_7.9.alma.1
AlmaLinux:9rhel-net-naming-sysattrsbefore 252-67.el9_8.2.alma.1252-67.el9_8.2.alma.1
AlmaLinux:9systemdbefore 252-67.el9_8.2.alma.1252-67.el9_8.2.alma.1
AlmaLinux:9systemdbefore 252-55.el9_7.9.alma.1252-55.el9_7.9.alma.1
AlmaLinux:9systemd-boot-unsignedbefore 252-67.el9_8.2.alma.1252-67.el9_8.2.alma.1
AlmaLinux:9systemd-boot-unsignedbefore 252-55.el9_7.9.alma.1252-55.el9_7.9.alma.1
AlmaLinux:9systemd-containerbefore 252-67.el9_8.2.alma.1252-67.el9_8.2.alma.1
AlmaLinux:9systemd-containerbefore 252-55.el9_7.9.alma.1252-55.el9_7.9.alma.1
AlmaLinux:9systemd-develbefore 252-67.el9_8.2.alma.1252-67.el9_8.2.alma.1
AlmaLinux:9systemd-develbefore 252-55.el9_7.9.alma.1252-55.el9_7.9.alma.1

+96

Same product

systemd project: all records

Other highest-scoring records for the same primary product.

  • CVE-2017-9445In systemd through 233, certain sizes passed to dns_packet_new in systemd-resolved can cause it to allocate a buffer that's too small.
    46Plan
  • CVE-2018-21029systemd 239 through 245 accepts any certificate signed by a trusted certificate authority for DNS Over TLS.
    40Plan
  • CVE-2015-7510Stack-based buffer overflow in the getpwnam and getgrnam functions of the NSS module nss-mymachines in systemd.
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2023-7008Dec 23, 2023 · Systemd-resolved: unsigned name response in signed zone is not refused when dnssec=yes
    23Monitor
  • ← EarlierCVE-2025-4598May 30, 2025 · Systemd-coredump: race condition that allows a local attacker to crash a suid program and gain read access to the resulting core dump
    18Monitor
  • Later →CVE-2026-40223Apr 10, 2026 · In systemd 258 before 260, a local unprivileged user can trigger an assert when a Delegate=yes and User=<unset> unit exists and is running.
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
azl3 systemd-bootstrap 250.3-19 on Azure Linux 3.0250.3-19 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 systemd-bootstrap 250.3-13 on CBL Mariner 2.0250.3-14 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 systemd-bootstrap 250.3-14 on CBL Mariner 2.0250.3-14 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 systemd-bootstrap 250.3-14 on CBL-Mariner 2.0Release NotesMicrosoft (MSRC)
almalinux:rhel-net-naming-sysattrs252-55.el9_7.9.alma.1 · AlmaLinux:9Package registry (OSV)
almalinux:systemd252-55.el9_7.9.alma.1 · AlmaLinux:9Package registry (OSV)
almalinux:systemd-boot-unsigned252-55.el9_7.9.alma.1 · AlmaLinux:9Package registry (OSV)
almalinux:systemd-container252-55.el9_7.9.alma.1 · AlmaLinux:9Package registry (OSV)
almalinux:systemd-devel252-55.el9_7.9.alma.1 · AlmaLinux:9Package registry (OSV)
almalinux:systemd-journal-remote252-55.el9_7.9.alma.1 · AlmaLinux:9Package registry (OSV)
almalinux:systemd-libs252-55.el9_7.9.alma.1 · AlmaLinux:9Package registry (OSV)
almalinux:systemd-oomd252-55.el9_7.9.alma.1 · AlmaLinux:9Package registry (OSV)
almalinux:systemd-pam252-55.el9_7.9.alma.1 · AlmaLinux:9Package registry (OSV)
almalinux:systemd-resolved252-55.el9_7.9.alma.1 · AlmaLinux:9Package registry (OSV)
almalinux:systemd-rpm-macros257-13.el10_1.3.alma.1 · AlmaLinux:10Package registry (OSV)
almalinux:systemd-ukify257-13.el10_1.3.alma.1 · AlmaLinux:10Package registry (OSV)
debian:systemd252.39-1~deb12u2 · Debian:12Package registry (OSV)
opensuse:systemd254.27-150600.4.62.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:systemd-mini257.13-160000.4.1 · openSUSE:Leap 16.0Package registry (OSV)
red hat:systemd-boot-unsigned0:257-13.el10_1.3 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:systemd-container-debuginfo0:257-13.el10_1.3 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:systemd-debuginfo0:257-13.el10_1.3 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:systemd-debugsource0:257-13.el10_1.3 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:systemd-devel0:257-13.el10_1.3 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:systemd-journal-remote0:257-13.el10_1.3 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:systemd-journal-remote-debuginfo0:257-13.el10_1.3 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:systemd-libs-debuginfo0:257-13.el10_1.3 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:systemd-oomd-debuginfo0:257-13.el10_1.3 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:systemd-pam-debuginfo0:257-13.el10_1.3 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:systemd-resolved-debuginfo0:257-13.el10_1.3 · Red Hat:enterprise_linux:10.1Package registry (OSV)

+4

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-269 · Improper Privilege Management

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-secondary

Root cause

To simplify setup, a service account is granted broad, cluster-wide permissions. The principle of least privilege is skipped during installation.

The bug in code

The whole CWE-269 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

yaml
kind: ClusterRolerules:  - apiGroups: ["*"]    resources: ["*"]    verbs: ["*"]

Fixed

yaml
kind: Rolemetadata:  namespace: lodos-systemrules:  - apiGroups: ["apps"]    resources: ["deployments"]    verbs: ["get", "list", "update"]

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (10 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records