CVE
Yggdrasil-worker-package-manager: yggdrasil-worker-package-manager: path traversal via unsanitized repo name in addrepo/removerepo
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. The yggdrasil-worker-package-manager worker runs as root via its systemd unit. Exploitation requires malformed directives dispatched through the management message broker.
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 32/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
An authenticated attacker in Red Hat Enterprise Linux 10 can exploit a path traversal flaw in yggdrasil-worker-package-manager by supplying a crafted repository name to the repository add and remove operations. Because the root-level worker process then acts on files outside the intended directory, the attacker can modify or delete host files and may be able to escalate privileges.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
A flaw was found in yggdrasil-worker-package-manager. An authenticated attacker can exploit this issue to achieve arbitrary file modification or potential privilege escalation. The vulnerability exists because repository management operations fail to sanitize directory traversal sequences (such as '../') within repository names. By supplying a crafted repository name, an attacker can manipulate the root-level worker process into creating or deleting files outside the intended directory, compromising host system integrity.
Who should check
Red Hat Enterprise Linux 10 hosts running yggdrasil-worker-package-manager as root, especially those accepting repo directives from a management message broker.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Shipped in major Linux distributions
- Severity8.8/10CVSS 8.8
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 82 if added to CISA KEV
- Would score about 77 if CISA's SSVC rates exploitation active
- Would score about 39 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
The yggdrasil-worker-package-manager worker runs as root via its systemd unit. Exploitation requires malformed directives dispatched through the management message broker.Workaround: Restrict and audit authenticated access to dispatch directives through the management message broker.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-18379 (Yggdrasil-worker-package-manager: yggdrasil-worker-package-manager: path traversal via unsanitized repo name in addrepo/removerepo), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-18379 (entry last updated 2026-11-12):
Affected:
- Red Hat Red Hat Enterprise Linux 10: version range not reported
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- The yggdrasil-worker-package-manager worker runs as root via its systemd unit. (source: https://bugzilla.redhat.com/show_bug.cgi?id=2546571)
- Exploitation requires malformed directives dispatched through the management message broker. (source: https://access.redhat.com/security/cve/cve-2026-18379)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
Workaround: Restrict and audit authenticated access to dispatch directives through the management message broker. (source: https://bugzilla.redhat.com/show_bug.cgi?id=2546571)
CISA KEV: CVE-2026-18379 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-18379 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://bugzilla.redhat.com/show_bug.cgi?id=2546571
- https://access.redhat.com/security/cve/CVE-2026-18379
- https://access.redhat.com/security/cve/cve-2026-18379
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-18379
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-18379"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- yggdrasil-worker-package-manager
Version range not reported
Evidence 3
Write-ups · 1
Establishes: Technical detail and context.
- Report
Other links · 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-18379
Is CVE-2026-18379 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The repo name passed to addrepo and removerepo is not sanitized, which allows path traversal. An authenticated attacker can use this to modify or delete files outside the repository directory, possibly escalating privileges and compromising host integrity.Source: bugzilla.redhat.com, access.redhat.com
Am I affected, and how do I check?
The checked facts name Red Hat Enterprise Linux 10 and the yggdrasil-worker-package-manager worker, which runs as root through its systemd unit. No affected version numbers are given. To check a host, confirm whether the worker is installed and whether its systemd unit is present and running.Source: bugzilla.redhat.com, access.redhat.com
How do I fix CVE-2026-18379?
The checked facts do not name fixed versions or patch identifiers, so the upgrade target is not stated. The only remedy named is restricting and auditing authenticated access to dispatch directives through the management message broker.Source: bugzilla.redhat.com, access.redhat.com
What if there's no patch?
Restrict and audit authenticated access to dispatching directives through the management message broker. This is the only workaround named in the checked facts.Source: bugzilla.redhat.com, access.redhat.com