CVE-2026-46160

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory (severity: MODERATE) published 2026-05-28. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2026-32787 (ENISA EUVD) · GHSA-xvrh-2655-9jjv (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
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.1%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

btrfs: fix missing last_unlink_trans update when removing a directory

When removing a directory we are not updating its last_unlink_trans field, which can result in incorrect fsync behaviour in case some one fsyncs the directory after it was removed because it's holding a file descriptor on it.

Example scenario:

mkdir /mnt/dir1 mkdir /mnt/dir1/dir2 mkdir /mnt/dir3

sync -f /mnt

# Do some change to the directory and fsync it. chmod 700 /mnt/dir1 xfs_io -c fsync /mnt/dir1

# Move dir2 out of dir1 so that dir1 becomes empty. mv /mnt/dir1/dir2 /mnt/dir3/

open fd on /mnt/dir1 call rmdir(2) on path "/mnt/dir1" fsync fd

When attempting to mount the filesystem, the log replay will fail with an -EIO error and dmesg/syslog has the following:

[445771.626482] BTRFS info (device dm-0): first mount of filesystem 0368bbea-6c5e-44b5-b409-09abe496e650 [445771.626486] BTRFS info (device dm-0): using crc32c checksum algorithm [445771.627912] BTRFS info (device dm-0): start tree-log replay [445771.628335] page: refcount:2 mapcount:0 mapping:0000000061443ddc index:0x1d00 pfn:0x7072a5 [445771.629453] memcg:ffff89f400351b00 [445771.629892] aops:btree_aops [btrfs] ino:1 [445771.630737] flags: 0x17fffc00000402a(uptodate|lru|private|writeback|node=0|zone=2|lastcpupid=0x1ffff) [445771.632359] raw: 017fffc00000402a fffff47284d950c8 fffff472907b7c08 ffff89f458e412b8 [445771.633713] raw: 0000000000001d00 ffff89f6c51d1a90 00000002ffffffff ffff89f400351b00 [445771.635029] page dumped because: eb page dump [445771.635825] BTRFS critical (device dm-0): corrupt leaf: root=5 block=30408704 slot=10 ino=258, invalid nlink: has 2 expect no more than 1 for dir [445771.638088] BTRFS info (device dm-0): leaf 30408704 gen 10 total ptrs 17 free space 14878 owner 5 [445771.638091] BTRFS info (device dm-0): refs 4 lock_owner 0 current 3581087 [445771.638094] item 0 key (256 INODE_ITEM 0) itemoff 16123 itemsize 160 [445771.638097] inode generation 3 transid 9 size 16 nbytes 16384 [445771.638098] block group 0 mode 40755 links 1 uid 0 gid 0 [445771.638100] rdev 0 sequence 2 flags 0x0 [445771.638102] atime 1775744884.0 [445771.660056] ctime 1775744885.645502983 [445771.660058] mtime 1775744885.645502983 [445771.660060] otime 1775744884.0 [445771.660062] item 1 key (256 INODE_REF 256) itemoff 16111 itemsize 12 [445771.660064] index 0 name_len 2 [445771.660066] item 2 key (256 DIR_ITEM 1843588421) itemoff 16077 itemsize 34 [445771.660068] location key (259 1 0) type 2 [445771.660070] transid 9 data_len 0 name_len 4 [445771.660075] item 3 key (256 DIR_ITEM 2363071922) itemoff 16043 itemsize 34 [445771.660076] location key (257 1 0) type 2 [445771.660077] transid 9 data_len 0 name_len 4 [445771.660078] item 4 key (256 DIR_INDEX 2) itemoff 16009 itemsize 34 [445771.660079] location key (257 1 0) type 2 [445771.660080] transid 9 data_len 0 name_len 4 [445771.660081] item 5 key (256 DIR_INDEX 3) itemoff 15975 itemsize 34 [445771.660082] location key (259 1 0) type 2 [445771.660083] transid 9 data_len 0 name_len 4 [445771.660084] item 6 key (257 INODE_ITEM 0) itemoff 15815 itemsize 160 [445771.660086] inode generation 9 transid 9 size 8 nbytes 0 [445771.660087] block group 0 mode 40777 links 1 uid 0 gid 0 [445771.660088] rdev 0 sequence 2 flags 0x0 [445771.660089] atime 1775744885.641174097 [445771.660090] ctime 1775744885.645502983 [445771.660091] mtime 1775744885.645502983 [445771.660105] otime 1775744885.641174097 [445771.660106] item 7 key (257 INODE_REF 256) itemoff 15801 itemsize 14 [445771.660107] index 2 name_len 4 [445771.660108] item 8 key (257 DIR_ITEM 2676584006) itemoff 15767 itemsize 34 [445771.660109] location key (2 ---truncated---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 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.1%
EPSS %ILE
2nd
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-06). 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, and whom BOD 26-04 binds: 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.

The score's inputs: 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

May 28, 2026

Last Modified

November 6, 2026

Advisory Details (8)

Auto-updated Jun 19, 2026
Patch available.
Web page

btrfs: fix missing last_unlink_trans update when removing a directory - kernel/git/stable/linux.git - Linux kernel stable tree

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

btrfs: fix missing last_unlink_trans update when removing a directory - kernel/git/stable/linux.git - Linux kernel stable tree

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

btrfs: fix missing last_unlink_trans update when removing a directory - kernel/git/stable/linux.git - Linux kernel stable tree

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

btrfs: fix missing last_unlink_trans update when removing a directory - kernel/git/stable/linux.git - Linux kernel stable tree

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

btrfs: fix missing last_unlink_trans update when removing a directory - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/999757231c49376cd1a37308d2c8c4c9932571e1
Web page

btrfs: fix missing last_unlink_trans update when removing a directory - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6acbb2f6dff23c9bb9761fb98b516525b9cf1ce9
Web page

btrfs: fix missing last_unlink_trans update when removing a directory - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/36fcc2c7517f8a86379154c9793f867592aa8b7e
Web page

btrfs: fix missing last_unlink_trans update when removing a directory - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2525998ac956476bded26b9f34c4164dc890b87a

Vendor Advisories for CVE-2026-46160(2)

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

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-10-22ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-10-22ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-10-22ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-10-22ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-10-22ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-10-22ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-10-22ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-10-22ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-10-22ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-10-22ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-10-22ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-10-22ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-10-22ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-10-22ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-10-22ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-10-22ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-10-22ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-10-22ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-10-22ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-10-22ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-10-22ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-10-22ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-22ubuntu
ubuntulinux-tools-azure-edge (7.0.0-1014.14~24.04.1) @ noble2026-10-22ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-22ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1122.131) @ jammy2026-10-22ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1114.120~20.04.1) @ focal2026-10-22ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1118.128~20.04.1) @ focal2026-10-22ubuntu
ubuntulinux-tools-gcp-lts-22.04 (5.15.0.1118.115) @ jammy2026-10-22ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1080 (5.15.0-1080.84) @ jammy2026-10-22ubuntu
linuxKernel @ 5.10.259 (fixes >=2.6.30)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)
  • every version up to 5.10.259-1: fixed in 5.10.259-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)
  • every version up to 6.1.176-1~deb11u1: fixed in 6.1.176-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)
  • every version up to 6.1.176-1: fixed in 6.1.176-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)
  • every version up to 6.12.94-1: fixed in 6.12.94-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.7-1~bpo13+1 (137 versions)
  • every version up to 7.0.7-1: fixed in 7.0.7-1
—

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 12× in last 7d / 45× 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 100 of 291 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. None are among the latest 100 rows. The 191 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-46160?
CVE-2026-46160 is a medium-severity vulnerability; its CVE record was published on May 28, 2026. In the Linux kernel, the following vulnerability has been resolved: btrfs: fix missing last_unlink_trans update when removing a directory When removing a directory we are not updating its last_unlink_trans field, which can result in incorrect fsync behaviour in case some one fsyncs the directory…
When was the CVE record for CVE-2026-46160 published?
The CVE record for CVE-2026-46160 was published on May 28, 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 November 6, 2026; the record at its source may have been updated since.
Is CVE-2026-46160 actively exploited?
CVE-2026-46160 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-46160?
CVE-2026-46160 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-46160?
A fix for CVE-2026-46160 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-46160 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-46160

Explore →

Is Your Infrastructure Affected by CVE-2026-46160?

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