CVE-2026-29051

LOWNVD 3.33.3
EchelonGraph scoreMEDIUM confidence

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

This low-severity CVE scores 3.3 under NVD CVSS v3. EPSS exploit probability: 0.2% (6th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-25356 (ENISA EUVD)Source: ENISA EUVD

3.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.2%CVSS: 3.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

melange allows users to build apk packages using declarative pipelines. Starting in version 0.32.0 and prior to version 0.43.4, melange lint --persist-lint-results (opt-in flag, also usable via melange build --persist-lint-results) constructs output file paths by joining --out-dir with the arch and pkgname values read from the .PKGINFO control file of the APK being linted. In affected versions these values were not validated for path separators or .. sequences, so an attacker who can supply an APK to a melange-based lint/build pipeline (e.g. CI that lints third-party APKs, or build-as-a-service) could cause melange to write lint---r.json to an arbitrary .json path reachable by the melange process. The written file is a JSON lint report whose content is partially attacker-influenced. There is no direct code-execution path, but the write can clobber other JSON artifacts on the filesystem. The issue only affects deployments that explicitly pass --persist-lint-results; the flag is off by default. The issue is fixed in melange v0.43.4 by validating arch and pkgname for .., /, and filepath.Separator before path construction in pkg/linter/results.go (commit 84f3b45). As a workaround, do not pass --persist-lint-results when linting or building APKs whose .PKGINFO contents are not fully trusted. Running melange as a low-privileged user and confining writes to an isolated directory also limits impact.

CVSS v3
3.3
EG Score
3.3LOWmedium confidence
EG Risk
15
EG Risk 15/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity33% × 45%
Impact severity (EG Severity): CVSS 3.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 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.2%
EPSS %ILE
6th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (3.3): severity, escalated by confirmed exploitation. This CVE's 3.3 is its impact severity (EG Severity), not escalated.

EG Severity
3.3 LOWCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-26). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

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

April 24, 2026

Last Modified

October 26, 2026

Advisory Details (2)

Auto-updated Aug 2, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Path traversal in melange --persist-lint-results via unvalidated .PKGINFO fields · Advisory · chainguard-dev/melange · GitHub

https://github.com/chainguard-dev/melange/security/advisories/GHSA-q2pw-xx38-p64j
GitHub commit

commit 84f3b450ce6e (chainguard-dev/melange)

Fix landed in chainguard-dev/melange commit 84f3b450ce6e — awaiting tagged release

https://github.com/chainguard-dev/melange/commit/84f3b450ce6e472c4abb8dc4c26d0ce8ac1259ac

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
chainguard.dev/melange—
  • 0.32.0 up to 0.43.4: fixed in 0.43.4
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 38× 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.

Showing the most recent 96 of 217 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 121 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  2. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  3. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  4. 2026-10-26 22:46 UTCEG score recompute▼ 1.10
  5. 2026-10-26 22:26 UTCNVD updateCVSS v3 → 3.3 · severity → LOW
  6. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  7. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  8. 2026-10-25 14:37 UTCEG score recompute
  9. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  10. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  11. 2026-10-23 03:57 UTCEG score recompute
  12. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  13. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  14. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  15. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  16. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  17. 2026-10-18 03:49 UTCEG score recompute
  18. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  19. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  20. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  21. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  22. 2026-10-13 23:24 UTCOSV refresh
  23. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  24. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  25. 2026-10-12 16:16 UTCEG score recompute
Show 71 more
  1. 2026-10-11 19:58 UTCEG score recompute
  2. 2026-10-11 17:11 UTCEG score recompute
  3. 2026-10-11 14:41 UTCEG score recompute
  4. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  6. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  7. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  8. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  9. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  10. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  11. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  12. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  13. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  14. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  15. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  16. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  17. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  18. 2026-09-23 08:53 UTCOSV refresh
  19. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  20. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  21. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  22. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  23. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  24. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  25. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  26. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  27. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  28. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  29. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  30. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  31. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  32. 2026-09-04 03:29 UTCOSV refresh
  33. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  34. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  35. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  36. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  37. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  38. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  39. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  40. 2026-08-24 14:17 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  41. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  42. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  43. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  44. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  45. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  46. 2026-08-17 14:55 UTCEG score recompute
  47. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  48. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  49. 2026-08-16 05:51 UTCEG score recompute
  50. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  51. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  52. 2026-08-14 04:11 UTCEG score recompute
  53. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  54. 2026-08-12 17:55 UTCEG score recompute
  55. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  56. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  57. 2026-08-11 05:31 UTCEG score recompute
  58. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  59. 2026-08-10 04:27 UTCEG score recompute
  60. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  61. 2026-08-09 03:23 UTCEG score recompute
  62. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  63. 2026-08-07 12:39 UTCEG score recompute
  64. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  65. 2026-08-05 22:58 UTCEG score recompute
  66. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  67. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  68. 2026-08-03 21:08 UTCEG score recompute
  69. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  70. 2026-08-02 11:28 UTCEG score recompute
  71. 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.2% · 6th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-29051?
CVE-2026-29051 is a low-severity vulnerability; its CVE record was published on April 24, 2026. melange allows users to build apk packages using declarative pipelines. Starting in version 0.32.0 and prior to version 0.43.4, melange lint --persist-lint-results (opt-in flag, also usable via melange build --persist-lint-results) constructs output file paths by joining --out-dir with the arch and…
When was the CVE record for CVE-2026-29051 published?
The CVE record for CVE-2026-29051 was published on April 24, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 26, 2026; the record at its source may have been updated since.
Is CVE-2026-29051 actively exploited?
CVE-2026-29051 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-29051?
CVE-2026-29051 has a CVSS v3 base score of 3.3 (NVD).
How do I remediate CVE-2026-29051?
A fix for CVE-2026-29051 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-29051

Explore →

Is Your Infrastructure Affected by CVE-2026-29051?

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

Book a Demo →Browse All CVEs