CVE-2026-43080

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 published 2026-05-06. 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 — 3 sources updated this week

Also known asEUVD-2026-27571 (ENISA EUVD) · GHSA-pmcg-f5m4-2gwp (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:

l2tp: Drop large packets with UDP encap

syzbot reported a WARN on my patch series [1]. The actual issue is an overflow of 16-bit UDP length field, and it exists in the upstream code. My series added a debug WARN with an overflow check that exposed the issue, that's why syzbot tripped on my patches, rather than on upstream code.

syzbot's repro:

r0 = socket$pppl2tp(0x18, 0x1, 0x1) r1 = socket$inet6_udp(0xa, 0x2, 0x0) connect$inet6(r1, &(0x7f00000000c0)={0xa, 0x0, 0x0, @loopback, 0xfffffffc}, 0x1c) connect$pppl2tp(r0, &(0x7f0000000240)=@pppol2tpin6={0x18, 0x1, {0x0, r1, 0x4, 0x0, 0x0, 0x0, {0xa, 0x4e22, 0xffff, @ipv4={'\x00', '\xff\xff', @empty}}}}, 0x32) writev(r0, &(0x7f0000000080)=[{&(0x7f0000000000)="ee", 0x34000}], 0x1)

It basically sends an oversized (0x34000 bytes) PPPoL2TP packet with UDP encapsulation, and l2tp_xmit_core doesn't check for overflows when it assigns the UDP length field. The value gets trimmed to 16 bites.

Add an overflow check that drops oversized packets and avoids sending packets with trimmed UDP length to the wire.

syzbot's stack trace (with my patch applied):

len >= 65536u WARNING: ./include/linux/udp.h:38 at udp_set_len_short include/linux/udp.h:38 [inline], CPU#1: syz.0.17/5957 WARNING: ./include/linux/udp.h:38 at l2tp_xmit_core net/l2tp/l2tp_core.c:1293 [inline], CPU#1: syz.0.17/5957 WARNING: ./include/linux/udp.h:38 at l2tp_xmit_skb+0x1204/0x18d0 net/l2tp/l2tp_core.c:1327, CPU#1: syz.0.17/5957 Modules linked in: CPU: 1 UID: 0 PID: 5957 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 RIP: 0010:udp_set_len_short include/linux/udp.h:38 [inline] RIP: 0010:l2tp_xmit_core net/l2tp/l2tp_core.c:1293 [inline] RIP: 0010:l2tp_xmit_skb+0x1204/0x18d0 net/l2tp/l2tp_core.c:1327 Code: 0f 0b 90 e9 21 f9 ff ff e8 e9 05 ec f6 90 0f 0b 90 e9 8d f9 ff ff e8 db 05 ec f6 90 0f 0b 90 e9 cc f9 ff ff e8 cd 05 ec f6 90 <0f> 0b 90 e9 de fa ff ff 44 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c 4f RSP: 0018:ffffc90003d67878 EFLAGS: 00010293 RAX: ffffffff8ad985e3 RBX: ffff8881a6400090 RCX: ffff8881697f0000 RDX: 0000000000000000 RSI: 0000000000034010 RDI: 000000000000ffff RBP: dffffc0000000000 R08: 0000000000000003 R09: 0000000000000004 R10: dffffc0000000000 R11: fffff520007acf00 R12: ffff8881baf20900 R13: 0000000000034010 R14: ffff8881a640008e R15: ffff8881760f7000 FS: 000055557e81f500(0000) GS:ffff8882a9467000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000200000033000 CR3: 00000001612f4000 CR4: 00000000000006f0 Call Trace: pppol2tp_sendmsg+0x40a/0x5f0 net/l2tp/l2tp_ppp.c:302 sock_sendmsg_nosec net/socket.c:727 [inline] __sock_sendmsg net/socket.c:742 [inline] sock_write_iter+0x503/0x550 net/socket.c:1195 do_iter_readv_writev+0x619/0x8c0 fs/read_write.c:-1 vfs_writev+0x33c/0x990 fs/read_write.c:1059 do_writev+0x154/0x2e0 fs/read_write.c:1105 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f636479c629 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffffd4241c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000014 RAX: ffffffffffffffda RBX: 00007f6364a15fa0 RCX: 00007f636479c629 RDX: 0000000000000001 RSI: 0000200000000080 RDI: 0000000000000003 RBP: 00007f6364832b39 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f6364a15fac R14: 00007f6364a15fa0 R15: 00007f6364a15fa0

[1]: https://lore.kernel.org/all/[email protected]/

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 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.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-10-24). 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: 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.

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

May 6, 2026

Last Modified

October 15, 2026

Advisory Details (8)

Auto-updated Aug 2, 2026
Patch available.
Web page

l2tp: Drop large packets with UDP encap - kernel/git/stable/linux.git - Linux kernel stable tree

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

l2tp: Drop large packets with UDP encap - kernel/git/stable/linux.git - Linux kernel stable tree

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

l2tp: Drop large packets with UDP encap - kernel/git/stable/linux.git - Linux kernel stable tree

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

l2tp: Drop large packets with UDP encap - kernel/git/stable/linux.git - Linux kernel stable tree

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

l2tp: Drop large packets with UDP encap - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9ccce02d501335f59a02f26c878c5e095b16302f
Web page

l2tp: Drop large packets with UDP encap - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/86534c97abd6365a9a021fd767a2023e63c44469
Web page

l2tp: Drop large packets with UDP encap - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/77c1489398c85a844f90205f5e76fd6bc8bb4089
Web page

l2tp: Drop large packets with UDP encap - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/02d787fd0922c71c0264449fe82d35983613e4e5

Vendor Advisories for CVE-2026-43080(1)

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

Patch Availability(28)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-aws-edge (6.8.0-1061.64~22.04.1) @ jammy2026-10-15ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-10-15ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-10-15ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-10-15ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-10-15ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-10-15ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-10-15ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-10-15ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-10-15ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1106.104) @ jammy2026-10-15ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-10-15ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-10-15ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-10-15ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-10-15ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-10-15ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-10-15ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1056.57~22.04.2) @ jammy2026-10-15ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1106.110~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-10-15ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-10-15ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-10-15ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-10-15ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-10-15ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-10-15ubuntu
linuxKernel @ 5.10.258 (fixes >=2.6.23)—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.85-1~bpo12+1 (17 versions)
  • every version up to 6.12.85-1: fixed in 6.12.85-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (130 versions)
  • every version up to 6.19.14-1: fixed in 6.19.14-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 37× 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 225 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 125 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-43080?
CVE-2026-43080 is a medium-severity vulnerability; its CVE record was published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: l2tp: Drop large packets with UDP encap syzbot reported a WARN on my patch series [1]. The actual issue is an overflow of 16-bit UDP length field, and it exists in the upstream code. My series added a debug WARN with an overflow…
When was the CVE record for CVE-2026-43080 published?
The CVE record for CVE-2026-43080 was published on May 6, 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 15, 2026; the record at its source may have been updated since.
Is CVE-2026-43080 actively exploited?
CVE-2026-43080 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-43080?
CVE-2026-43080 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43080?
A fix for CVE-2026-43080 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-43080 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-43080

Explore →

Is Your Infrastructure Affected by CVE-2026-43080?

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

Book a Demo →Browse All CVEs