CVE-2026-68149

HIGHPre-NVD 8.48.4—
EchelonGraph scoreHIGH confidence

Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2026-08-10. a secondary CVSS source baseline 8.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.4Exploit: None knownExposed: 0

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

In the Linux kernel, the following vulnerability has been resolved:

fs: preserve ACL_DONT_CACHE state in forget_cached_acl()

The ACL_DONT_CACHE state is meant to be a constant state for the inode for filesystems that want to opt out of posix acl caching.

Commit facd61053cff1 ("fuse: fixes after adapting to new posix acl api") used this facility to opt out of posix acl caching for fuse inodes with fuse server that does not negotiate FUSE_POSIX_ACL (fc->posix_acl).

The commit also takes care to gate the forget_all_cached_acls() call in fuse_set_acl() on fc->posix_acl because there is no need for it, but there are other placed in fuse code which call forget_all_cached_acls() unconditional to fc->posix_acl and those cause the loss of the ACL_DONT_CACHE state.

This is not only a functional bug. Properly timed, a get_acl() from this fuse filesystem can return a stale cached value, as was observed in tests, because set_acl() does not invalidate the unintentional acl cache.

We could fix this in fuse, but it actually makes no sense for the vfs helper forget_cached_acl() to invalidate the ACL_DONT_CACHE state, so let it not do that to fix fuse and future users of ACL_DONT_CACHE.

CVSS v3
8.4
EG Score
8.4(high)
EG Risk
42(Track)
EG Risk 42/100SSVC: Track

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
Severity84% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 17, 2026

Advisory Details (5)

Auto-updated Aug 14, 2026
No patch confirmed yet.
generic

fs: preserve ACL_DONT_CACHE state in forget_cached_acl() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ca03a7984a34f48085fd013e0d2cf4e6420b4acf
generic

fs: preserve ACL_DONT_CACHE state in forget_cached_acl() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b98fad81f1202b0eb26aacf3ff4cc7a21ed3b5bf
generic

fs: preserve ACL_DONT_CACHE state in forget_cached_acl() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a019b074903b3ad0a9726087efd0e8291452023b
generic

fs: preserve ACL_DONT_CACHE state in forget_cached_acl() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/834ddf899484a2f23129080e8773bc04f4691d07
generic

fs: preserve ACL_DONT_CACHE state in forget_cached_acl() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4b9a5458d02e214ef2b384124ca626e3e381d778

Vendor Advisories for CVE-2026-68149(2)

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 30× in last 7d / 42× 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-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 21:18 UTCGHSA enrichment
  3. 2026-08-20 08:59 UTCGHSA enrichment
  4. 2026-08-19 20:41 UTCEG score recompute
  5. 2026-08-19 20:41 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 08:22 UTCGHSA enrichment
  8. 2026-08-18 20:03 UTCEG score recompute
  9. 2026-08-18 20:03 UTCGHSA enrichment
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-18 07:44 UTCGHSA enrichment
  12. 2026-08-17 19:21 UTCEG score recompute
  13. 2026-08-17 19:21 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 05:40 UTCEG score recompute
  16. 2026-08-17 05:40 UTCGHSA enrichment
  17. 2026-08-17 05:11 UTCEG score recompute
  18. 2026-08-17 05:11 UTCGHSA enrichment
  19. 2026-08-17 01:22 UTCEG score recompute
  20. 2026-08-17 01:22 UTCGHSA enrichment
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 13:03 UTCEG score recompute
  23. 2026-08-16 13:03 UTCGHSA enrichment
  24. 2026-08-16 00:45 UTCGHSA enrichment
  25. 2026-08-15 12:26 UTCEG score recompute
Show 17 more
  1. 2026-08-15 12:26 UTCGHSA enrichment
  2. 2026-08-15 01:30 UTCEPSS rescore
  3. 2026-08-15 00:07 UTCGHSA enrichment
  4. 2026-08-14 11:48 UTCEG score recompute
  5. 2026-08-14 11:48 UTCGHSA enrichment
  6. 2026-08-13 23:30 UTCEG score recompute
  7. 2026-08-13 23:30 UTCGHSA enrichment
  8. 2026-08-13 22:45 UTCEG score recompute▲ 8.40
  9. 2026-08-13 22:45 UTCGHSA enrichment
  10. 2026-08-13 22:44 UTCMITRE cvelistV5CVSS v3 → 8.4 · severity → HIGH
  11. 2026-08-13 22:00 UTCEPSS rescore
  12. 2026-08-13 17:52 UTCEG score recompute
  13. 2026-08-13 17:52 UTCGHSA enrichment
  14. 2026-08-12 13:51 UTCEPSS rescore
  15. 2026-08-10 13:24 UTCNVD update
  16. 2026-08-10 12:21 UTCEG score recompute
  17. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68149?
CVE-2026-68149 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: fs: preserve ACLDONTCACHE state in forgetcachedacl() The ACLDONTCACHE state is meant to be a constant state for the inode for filesystems that want to opt out of posix acl caching. Commit facd61053cff1 ("fuse: fixes after adapting…
When was CVE-2026-68149 disclosed?
CVE-2026-68149 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68149 actively exploited?
CVE-2026-68149 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.6% of all scored CVEs.
What is the CVSS score of CVE-2026-68149?
CVE-2026-68149 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-68149?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68149, 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-68149

Explore →

Is Your Infrastructure Affected by CVE-2026-68149?

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

Start Free Scan →Browse All CVEs