CVE-2026-74595

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: 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:

fscrypt: use the mount idmap for the owner check in fscrypt_ioctl_set_policy()

fscrypt_ioctl_set_policy() calls inode_owner_or_capable() with &nop_mnt_idmap before allowing an encryption policy to be set, instead of the idmap of the mount the ioctl was issued on.

fscrypt is used by filesystems that support idmapped mounts (e.g. ext4, f2fs), so on such a mount this compares the caller's fsuid against the unmapped on-disk owner rather than the mapped owner: the actual owner can be wrongly denied with -EACCES and an unrelated caller wrongly allowed. Use file_mnt_idmap(filp) instead.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

August 22, 2026

Last Modified

August 25, 2026

Advisory Details (7)

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

fscrypt: use the mount idmap for the owner check in fscrypt_ioctl_set_policy() - kernel/git/stable/linux.git - Linux kernel stable tree

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

fscrypt: use the mount idmap for the owner check in fscrypt_ioctl_set_policy() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/98516ba8b817f34e86bdd7a5b7a383cff75c3ddf
generic

fscrypt: use the mount idmap for the owner check in fscrypt_ioctl_set_policy() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/653e888a24c87b8bbeab44d7e558a1c1a3641088
generic

fscrypt: use the mount idmap for the owner check in fscrypt_ioctl_set_policy() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6a67c460b12315033268dce597546984fe5739e7
generic

fscrypt: use the mount idmap for the owner check in fscrypt_ioctl_set_policy() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/33b7e810ce09955aa02f3b632455cf5e7ac990a9
generic

fscrypt: use the mount idmap for the owner check in fscrypt_ioctl_set_policy() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0baeb730044981f5ec5fb7d62a3763835ea606f6
generic

fscrypt: use the mount idmap for the owner check in fscrypt_ioctl_set_policy() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/174633a468817a49bd474bcfc9067c84e54efe68

Vendor Advisories for CVE-2026-74595(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 26× in last 7d / 29× 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-29 23:19 UTCGHSA enrichment
  2. 2026-08-29 12:14 UTCGHSA enrichment
  3. 2026-08-29 00:59 UTCEG score recompute
  4. 2026-08-29 00:58 UTCGHSA enrichment
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-28 12:40 UTCGHSA enrichment
  7. 2026-08-28 01:34 UTCGHSA enrichment
  8. 2026-08-27 14:29 UTCEG score recompute
  9. 2026-08-27 14:29 UTCGHSA enrichment
  10. 2026-08-27 14:25 UTCEPSS rescore
  11. 2026-08-27 03:22 UTCGHSA enrichment
  12. 2026-08-26 16:13 UTCGHSA enrichment
  13. 2026-08-26 04:41 UTCGHSA enrichment
  14. 2026-08-25 17:35 UTCEG score recompute
  15. 2026-08-25 17:35 UTCGHSA enrichment
  16. 2026-08-25 13:49 UTCEPSS rescore
  17. 2026-08-25 06:30 UTCEG score recompute
  18. 2026-08-25 06:30 UTCGHSA enrichment
  19. 2026-08-25 05:45 UTCEG score recompute▲ 7.80
  20. 2026-08-25 05:45 UTCGHSA enrichment
  21. 2026-08-25 05:45 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  22. 2026-08-24 14:18 UTCEPSS rescore
  23. 2026-08-23 13:19 UTCGHSA enrichment
  24. 2026-08-23 13:19 UTCNVD update
  25. 2026-08-23 13:06 UTCGHSA enrichment
Show 4 more
  1. 2026-08-23 13:05 UTCMITRE cvelistV5
  2. 2026-08-22 16:24 UTCNVD update
  3. 2026-08-22 15:42 UTCEG score recompute
  4. 2026-08-22 15:35 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74595?
CVE-2026-74595 is a high vulnerability published on August 22, 2026. In the Linux kernel, the following vulnerability has been resolved: fscrypt: use the mount idmap for the owner check in fscryptioctlset_policy() fscryptioctlsetpolicy() calls inodeownerorcapable() with &nopmntidmap before allowing an encryption policy to be set, instead of the idmap of the mount…
When was CVE-2026-74595 disclosed?
CVE-2026-74595 was first published in the National Vulnerability Database on August 22, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74595 actively exploited?
CVE-2026-74595 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 99.4% of all scored CVEs.
What is the CVSS score of CVE-2026-74595?
CVE-2026-74595 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-74595?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74595, 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-74595

Explore →

Is Your Infrastructure Affected by CVE-2026-74595?

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

Start Free Scan →Browse All CVEs