CVE-2026-105768

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (21st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
6.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (Chainguard, Inc.) states them: "Upgrade to apko 1.4.5 or later, which rejects UID and GID values outside 0 to 4294967295 instead of truncating them."

apko allows users to build and publish OCI container images built from apk packages. From version 0.2.0 to before version 1.4.5, UserEntry.Parse and GroupEntry.Parse in pkg/passwd read the UID and GID fields of /etc/passwd and /etc/group entries with strconv.Atoi and convert them to uint32 without a range check. On 64-bit platforms an out-of-range value such as 4294967296 (2^32) is truncated to 0, and negative values wrap. Because apko parses the passwd and group entries supplied by the packages it installs and writes them back into the image, an attacker who controls a package installed into the image can ship an entry that appears to declare an unprivileged UID or GID but is written into the built image as UID 0 or GID 0 (root). The truncated UID is also used when resolving the image's run-as user. This issue has been fixed in version 1.4.5.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
28
EG Risk 28/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity63% × 45%
The EG Score, 6.3 of 10.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
21st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 5, 2026

Last Modified

October 6, 2026

Advisory Details (4)

Auto-updated Oct 5, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available

Release v1.4.5

Patch available: chainguard-dev/apko v1.4.5

https://github.com/chainguard-dev/apko/releases/tag/v1.4.5
GitHub commit

commit 739e7ce3f675 (chainguard-dev/apko)

Fix landed in chainguard-dev/apko commit 739e7ce3f675 — awaiting tagged release

https://github.com/chainguard-dev/apko/commit/739e7ce3f675ffb232e16849b51ff93657f1570c
GitHub pull request

fix(apko): fix CON-2732

Fix merged in chainguard-dev/apko PR #2516 on 2026-09-21 — awaiting tagged release

https://github.com/chainguard-dev/apko/pull/2516
GitHub advisoryMentions a patch (unverified)

UID/GID truncation in apko's /etc/passwd and /etc/group parsing writes package-supplied entries as root · Advisory · chainguard-dev/apko · GitHub

https://github.com/chainguard-dev/apko/security/advisories/GHSA-rj6x-hwpv-vhvf

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 21× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  2. 2026-10-12 16:39 UTCEG score recompute
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  4. 2026-10-11 20:15 UTCEG score recompute
  5. 2026-10-11 18:27 UTCEG score recompute
  6. 2026-10-11 15:01 UTCEG score recompute
  7. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  8. 2026-10-11 00:15 UTCEG score recompute
  9. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  10. 2026-10-09 21:55 UTCEG score recompute
  11. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  12. 2026-10-08 19:40 UTCEG score recompute
  13. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  14. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  15. 2026-10-07 17:00 UTCEG score recompute
  16. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  17. 2026-10-06 14:32 UTCEG score recompute
  18. 2026-10-06 14:10 UTCEG score recompute
  19. 2026-10-05 21:23 UTCEG score recompute
  20. 2026-10-05 21:09 UTCEG score recomputeFirst assessed: 6.3 MEDIUM
  21. 2026-10-05 21:05 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-105768?
CVE-2026-105768 is a medium-severity vulnerability; its CVE record was published on October 5, 2026. apko allows users to build and publish OCI container images built from apk packages. From version 0.2.0 to before version 1.4.5, UserEntry.Parse and GroupEntry.Parse in pkg/passwd read the UID and GID fields of /etc/passwd and /etc/group entries with strconv.Atoi and convert them to uint32 without…
When was CVE-2026-105768 made public?
CVE-2026-105768 was made public on September 23, 2026: that is the date its CVE record's CNA, Chainguard, Inc., gives for when the vulnerability was made public. The CVE record itself was published on October 5, 2026. EchelonGraph's copy of the record carries a last-modified date of October 6, 2026; the record at its source may have been updated since.
Is CVE-2026-105768 actively exploited?
CVE-2026-105768 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-105768?
CVE-2026-105768 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-105768?
A fix for CVE-2026-105768 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (Chainguard, Inc.) states them: "Upgrade to apko 1.4.5 or later, which rejects UID and GID values outside 0 to 4294967295 instead of truncating them."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-105768

Explore →

Is Your Infrastructure Affected by CVE-2026-105768?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs