CVE-2026-48785

MEDIUMPre-NVD 4.84.8
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 4.8 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:github_m
4.8
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: CVSS: 4.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Apptainer has incorrect path matching for 'limit container paths' directive

Impact

The limit container paths directive in apptainer.conf is intended to allow a system administrator limit the paths from which containers can be run, under setuid mode. Due to incorrect matching of a path string, sibling directories with similar names may incorrectly be allowed.

For example, the configuration:

limit container paths = /data/safe
Will also allow containers in /data/safe-but-unsafe to be run.

Patches

The issue is patched in apptainer version 1.5.1.

Workarounds

If developers do not use setuid mode or do not use the limit container paths functionality, then this issue does not affect their installation. Note that, as documented [1], if user namespaces are allowed for unrestricted use then this functionality does not stop users from running any container of their choice.

If developers do use the limit container paths functionality they are advised to update.

Credit

This vulnerability was discovered and disclosed to the Apptainer project by Dave Trudgian of Sylabs.

Resources

[1] https://apptainer.org/docs/admin/latest/configfiles.html#limiting-container-execution

CVSS v3
4.8
EG Score
4.8(low)
EPSS
KEV
Not listed

Published

June 26, 2026

Last Modified

June 26, 2026

Vendor Advisories for CVE-2026-48785(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 7× in last 7d / 11× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-06 15:07 UTCEG score recompute
  2. 2026-07-05 15:29 UTCEG score recompute
  3. 2026-07-04 15:51 UTCEG score recompute
  4. 2026-07-03 16:20 UTCEG score recompute
  5. 2026-07-02 16:48 UTCEG score recompute
  6. 2026-07-01 17:16 UTCEG score recompute
  7. 2026-06-30 17:45 UTCEG score recompute
  8. 2026-06-29 18:14 UTCEG score recompute
  9. 2026-06-28 18:40 UTCEG score recompute
  10. 2026-06-27 19:09 UTCEG score recompute
  11. 2026-06-26 19:37 UTCEG score recompute

Frequently asked(4)

What is CVE-2026-48785?
CVE-2026-48785 is a medium vulnerability published on June 26, 2026. Apptainer has incorrect path matching for 'limit container paths' directive Impact The limit container paths directive in apptainer.conf is intended to allow a system administrator limit the paths from which containers can be run, under setuid mode. Due to incorrect matching of a path string,…
When was CVE-2026-48785 disclosed?
CVE-2026-48785 was first published in the National Vulnerability Database on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-48785?
CVE-2026-48785 has a CVSS v4.0 base score of 4.8 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-48785?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48785, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-48785?

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