CVE-2026-74350

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-15. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-59497 (ENISA EUVD) · GHSA-c2hj-4vhc-jh3m (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

ocfs2: validate fast symlink target during inode read

ocfs2_validate_inode_block() already rejects several inconsistent self-contained dinodes before they are exposed to the rest of the filesystem. Fast symlinks need the same treatment.

A zero-cluster symlink is treated as a fast symlink and later read through page_get_link() and ocfs2_fast_symlink_read_folio(). That path uses strnlen() on the inline payload and then copies len + 1 bytes into the folio. If a corrupt dinode stores an i_size that does not fit the inline area or omits the terminating NUL at i_size, that copy reads past the end of the inode block buffer.

Reject zero-cluster symlink dinodes whose i_size exceeds the inline fast-symlink capacity or whose inline payload is not NUL-terminated exactly at i_size when the inode block is validated. This keeps malformed fast symlinks from reaching the read path.

Validation reproduced this kernel report: KASAN use-after-free in ocfs2_fast_symlink_read_folio+0x12c/0x1f0 RIP: 0033:0x7f5c6d859aa7 Read of size 3905 Call trace: dump_stack_lvl+0x66/0xa0 (?:?) print_report+0xce/0x630 (?:?) ocfs2_fast_symlink_read_folio+0x12c/0x1f0 (fs/ocfs2/inode.c:?) srso_alias_return_thunk+0x5/0xfbef5 (?:?) __virt_addr_valid+0x19f/0x330 (?:?) kasan_report+0xe0/0x110 (?:?) kasan_check_range+0x105/0x1b0 (?:?) __asan_memcpy+0x23/0x60 (?:?) filemap_read_folio+0x27/0xe0 (?:?) filemap_read_folio+0x35/0xe0 (?:?) do_read_cache_folio+0x138/0x230 (?:?) __page_get_link+0x26/0x110 (?:?) page_get_link+0x2e/0x70 (?:?) vfs_readlink+0x15e/0x250 (?:?) touch_atime+0x4d/0x370 (?:?) do_readlinkat+0x186/0x200 (?:?) do_user_addr_fault+0x65a/0x890 (?:?) __x64_sys_readlink+0x46/0x60 (?:?) do_syscall_64+0x115/0x6a0 (arch/x86/entry/syscall_64.c:87) entry_SYSCALL_64_after_hwframe+0x77/0x7f (?:?)

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
44
EG Risk 44/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.5%
EPSS %ILE
42nd
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

August 15, 2026

Last Modified

October 30, 2026

Advisory Details (6)

Auto-updated Nov 14, 2026
Patch available.
Web page

ocfs2: validate fast symlink target during inode read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f9e2cb692b77a679b1f4cc2b7b277fa908586533
Web page

ocfs2: validate fast symlink target during inode read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ed9f95ee3bbaea9b05808727eb86ea5e5ccf2b52
Web page

ocfs2: validate fast symlink target during inode read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e234973f286ed2e8961a24561ec91594ec3e3ff8
Web page

ocfs2: validate fast symlink target during inode read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dcabbf7da43825e23e5e89adccc1430faee1bce1
Web page

ocfs2: validate fast symlink target during inode read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d94bf50756d7f80bb728ad58246376649e1035b6
Web page

ocfs2: validate fast symlink target during inode read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/030d4caae89977b80349df95523dfda1dfb10f73

Vendor Advisories for CVE-2026-74350(2)

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

Patch Availability(27)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1067.70.1) @ noble2026-11-19ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1064.65) @ noble2026-11-19ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2056.58) @ noble2026-11-19ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1125.134) @ jammy2026-11-19ubuntu
ubuntulinux-tools-raspi2-hwe-18.04-edge (5.4.0.1149.180) @ focal2026-11-19ubuntu
ubuntulinux-tools-aws (4.4.0.1162.159) @ trusty2026-11-19ubuntu
ubuntulinux-tools-azure-lts-26.04 (7.0.0-1017.17) @ resolute2026-11-19ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-11-19ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1012.12~24.04.1) @ noble2026-11-19ubuntu
ubuntulinux-tools-fips (4.4.0.1133.135) @ xenial2026-11-19ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-34.34) @ resolute2026-11-19ubuntu
ubuntulinux-tools-gke-hwe-26.04 (7.0.0-1007.8) @ resolute2026-11-19ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1085 (5.4.0-1085.89) @ focal2026-11-19ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1071.78~22.04.1) @ jammy2026-11-19ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1113.111) @ jammy2026-11-19ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1014.14) @ resolute2026-11-19ubuntu
ubuntulinux-tools-azure-fde-edge (7.0.0-1016.16~24.04.1) @ noble2026-11-19ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.203.175) @ jammy2026-11-19ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2022.23) @ resolute2026-11-19ubuntu
ubuntulinux-tools-nvidia-64k-6.8 (6.8.0-1067.70) @ noble2026-11-19ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1071.78) @ noble2026-11-19ubuntu
ubuntulinux-virtual-lts-xenial (4.4.0.291.297) @ xenial2026-11-19ubuntu
ubuntulinux-vmware-tools-6.8.0-1010 (6.8.0-1010.10) @ noble2026-11-19ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1025.26) @ resolute2026-11-19ubuntu
ubuntulinux-tools-fips-5.15 (5.15.0.203.117) @ jammy2026-11-19ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-149.149~22.04.1) @ jammy2026-11-19ubuntu
linuxKernel @ 6.1.191 (fixes >=3.5.0)—osv

These rows come from Ubuntu and OSV. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.3~rc7-1~exp1 (375 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (38 versions)
  • every version up to 6.12.115-2: fixed in 6.12.115-2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (163 versions)
  • every version up to 7.1.5-1: fixed in 7.1.5-1
—

Additional Vendor Advisories

(24)

Data Freshness Timeline

(refreshed 20× in last 7d / 79× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 588 rows 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. None are among the latest 100 rows. The 488 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-22 13:42 UTCEchelonGraph re-scored
  2. 2026-11-22 13:42 UTCVendor advisory
  3. 2026-11-22 13:42 UTCGHSA enrichmentGHSA-c2hj-4vhc-jh3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-11-21 16:41 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  5. 2026-11-21 13:42 UTCEchelonGraph re-scored
  6. 2026-11-21 13:42 UTCVendor advisory
  7. 2026-11-21 13:42 UTCGHSA enrichmentGHSA-c2hj-4vhc-jh3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-11-20 16:38 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  9. 2026-11-20 13:42 UTCEchelonGraph re-scored
  10. 2026-11-20 13:42 UTCVendor advisory
  11. 2026-11-20 13:42 UTCGHSA enrichmentGHSA-c2hj-4vhc-jh3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-11-19 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  13. 2026-11-19 13:42 UTCEchelonGraph re-scored
  14. 2026-11-19 13:42 UTCVendor advisory
  15. 2026-11-19 13:42 UTCGHSA enrichmentGHSA-c2hj-4vhc-jh3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-11-18 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  17. 2026-11-18 13:42 UTCEchelonGraph re-scored
  18. 2026-11-18 13:42 UTCVendor advisory
  19. 2026-11-18 13:42 UTCGHSA enrichmentGHSA-c2hj-4vhc-jh3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-11-17 16:36 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  21. 2026-11-17 13:43 UTCEchelonGraph re-scored
  22. 2026-11-17 13:43 UTCVendor advisory
  23. 2026-11-17 13:43 UTCGHSA enrichmentGHSA-c2hj-4vhc-jh3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-11-16 16:52 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  25. 2026-11-16 13:43 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-11-16 13:43 UTCVendor advisory
  2. 2026-11-16 13:43 UTCGHSA enrichmentGHSA-c2hj-4vhc-jh3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-11-15 17:02 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  4. 2026-11-15 13:37 UTCEchelonGraph re-scored
  5. 2026-11-15 13:37 UTCVendor advisory
  6. 2026-11-15 13:36 UTCGHSA enrichmentGHSA-c2hj-4vhc-jh3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-11-14 16:41 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  8. 2026-11-14 13:37 UTCEchelonGraph re-scored
  9. 2026-11-14 13:37 UTCVendor advisory
  10. 2026-11-14 13:37 UTCGHSA enrichmentGHSA-c2hj-4vhc-jh3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-11-13 16:57 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  12. 2026-11-13 13:37 UTCEchelonGraph re-scored
  13. 2026-11-13 13:37 UTCGHSA enrichmentGHSA-c2hj-4vhc-jh3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  15. 2026-11-12 13:36 UTCEchelonGraph re-scored
  16. 2026-11-12 13:36 UTCGHSA enrichmentGHSA-c2hj-4vhc-jh3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  18. 2026-11-11 13:37 UTCEchelonGraph re-scored
  19. 2026-11-11 13:37 UTCGHSA enrichmentGHSA-c2hj-4vhc-jh3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  21. 2026-11-10 13:37 UTCEchelonGraph re-scored
  22. 2026-11-10 13:37 UTCGHSA enrichmentGHSA-c2hj-4vhc-jh3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  24. 2026-11-09 13:37 UTCEchelonGraph re-scored
  25. 2026-11-09 13:37 UTCGHSA enrichmentGHSA-c2hj-4vhc-jh3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  26. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  27. 2026-11-08 13:38 UTCEchelonGraph re-scored
  28. 2026-11-08 13:38 UTCGHSA enrichmentGHSA-c2hj-4vhc-jh3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  29. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  30. 2026-11-07 13:39 UTCEchelonGraph re-scored
  31. 2026-11-07 13:39 UTCGHSA enrichmentGHSA-c2hj-4vhc-jh3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  32. 2026-11-06 17:25 UTCOSV refresh
  33. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  34. 2026-11-06 13:39 UTCEchelonGraph re-scored
  35. 2026-11-06 13:39 UTCGHSA enrichmentGHSA-c2hj-4vhc-jh3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  36. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  37. 2026-11-05 13:40 UTCEchelonGraph re-scored
  38. 2026-11-05 13:40 UTCGHSA enrichmentGHSA-c2hj-4vhc-jh3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  39. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  40. 2026-11-04 13:41 UTCEchelonGraph re-scored
  41. 2026-11-04 13:41 UTCGHSA enrichmentGHSA-c2hj-4vhc-jh3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  42. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  43. 2026-11-03 13:42 UTCEchelonGraph re-scored
  44. 2026-11-03 13:42 UTCGHSA enrichmentGHSA-c2hj-4vhc-jh3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  46. 2026-11-02 13:26 UTCEchelonGraph re-scored
  47. 2026-11-02 13:26 UTCVendor advisory
  48. 2026-11-02 13:26 UTCGHSA enrichmentGHSA-c2hj-4vhc-jh3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  50. 2026-11-01 13:26 UTCEchelonGraph re-scored
  51. 2026-11-01 13:26 UTCVendor advisory
  52. 2026-11-01 13:26 UTCGHSA enrichmentGHSA-c2hj-4vhc-jh3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  53. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  54. 2026-10-31 13:27 UTCEchelonGraph re-scored
  55. 2026-10-31 13:27 UTCGHSA enrichmentGHSA-c2hj-4vhc-jh3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  56. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  57. 2026-10-30 13:27 UTCEchelonGraph re-scored
  58. 2026-10-30 13:27 UTCVendor advisory
  59. 2026-10-30 13:27 UTCGHSA enrichmentGHSA-c2hj-4vhc-jh3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  60. 2026-10-30 12:41 UTCEchelonGraph re-scored
  61. 2026-10-30 12:41 UTCVendor advisory
  62. 2026-10-30 12:41 UTCGHSA enrichmentGHSA-c2hj-4vhc-jh3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  63. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  64. 2026-10-29 14:53 UTCEchelonGraph re-scored
  65. 2026-10-29 14:53 UTCVendor advisory
  66. 2026-10-29 14:53 UTCGHSA enrichmentGHSA-c2hj-4vhc-jh3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  67. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  68. 2026-10-28 14:54 UTCEchelonGraph re-scored
  69. 2026-10-28 14:54 UTCVendor advisory
  70. 2026-10-28 14:53 UTCGHSA enrichmentGHSA-c2hj-4vhc-jh3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  71. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  72. 2026-10-27 14:24 UTCEchelonGraph re-scored
  73. 2026-10-27 14:24 UTCVendor advisory
  74. 2026-10-27 14:24 UTCGHSA enrichmentGHSA-c2hj-4vhc-jh3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  75. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile

Frequently asked(5)

What is CVE-2026-74350?
CVE-2026-74350 is a critical-severity vulnerability; its CVE record was published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: ocfs2: validate fast symlink target during inode read ocfs2_validate_inode_block() already rejects several inconsistent self-contained dinodes before they are exposed to the rest of the filesystem. Fast symlinks need the same…
When was the CVE record for CVE-2026-74350 published?
The CVE record for CVE-2026-74350 was published on August 15, 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 30, 2026; the record at its source may have been updated since.
Is CVE-2026-74350 actively exploited?
CVE-2026-74350 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-74350?
CVE-2026-74350 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-74350?
A fix for CVE-2026-74350 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-74350 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-74350?

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