What is the CVSS score of CVE-2026-61544?

CVE-2026-61544 has a CVSS 4.0 base score of 8.2 (High). CVSS vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N. EPSS exploitation probability: 0.2%.

Is there a public PoC exploit available for CVE-2026-61544?

Yes, a public proof-of-concept exploit is available for CVE-2026-61544. Prioritise patching immediately. EPSS: 0.2%.

Is there a patch available for CVE-2026-61544?

Yes, a patch is available for CVE-2026-61544. Update the affected software to the latest version immediately.

CVE-2026-61544

EUVD-2026-79501 HIGH

Uncaught Exception (CWE-248)

2026-09-15 security-advisories@github.com

GHSA-5hq8-qhww-jm7q

Information Disclosure

8.2

CVSS 4.0 · Vendor: github

View

Vulnerability Assessment

Weakness

CWE

CWE-248

OWASP Top 10:2025

A10:2025 - Mishandling of Exceptional Conditions

ASVS 5.0

V16 - Security Logging and Error Handling Exception handling completeness

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 15, 2026

Remote unauthenticated denial of service in the libp2p-quic transport crate (Rust implementation of libp2p) prior to 0.13.1: a peer that completes a valid-looking QUIC/TLS handshake with a deliberately short-lived libp2p TLS certificate and then withholds the final TLS 1.3 handshake fragment until that certificate expires triggers a wall-clock validity re-check in the post-handshake upgrade path, where an expect() call panics and tears down the application hosting the QUIC listener. Only a single inbound connection from a network peer is needed, no malformed packets are required, and the attack is fully automatable against any service exposing an affected libp2p-quic listener. The flaw is an uncaught exception (CWE-248) and is fixed in 0.13.1; no public exploit code and no CISA KEV listing were identified at time of analysis, though the GHSA advisory publishes a precise reproduction recipe.

Affected VersionsENISA

rust-libp2p < 0.13.1

Affected Packages

cargo libp2p-quic fix: 0.13.1

euvd rust_libp2p fix: 0.13.1

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in cargo, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Know when the next one hits your stack

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

Vendor (github) PRIMARY 8.2 HIGH

CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (github) · only source for this CVE.

CVSS VectorVendor: github

Attack Vector

Network

Attack Complexity

High

Attack Requirements

Present

Privileges Required

None

User Interaction

None

Vulnerable system: Confidentiality

None

Vulnerable system: Integrity

None

Vulnerable system: Availability

High

Subsequent system: Confidentiality

None

Subsequent system: Integrity

None

Subsequent system: Availability

None

Lifecycle Timeline

Patch available

Sep 15, 2026 - 21:20 EUVD

CVE Published

Sep 15, 2026 - 20:17 cve.org

HIGH 8.2

DescriptionCVE.org

libp2p-rust is the official Rust language implementation of the libp2p networking stack. Prior to 0.13.1, libp2p-quic could panic during an inbound QUIC handshake when a remote peer presented a valid short-lived libp2p TLS certificate and delayed the final TLS 1.3 handshake fragment until after the certificate expired. In the Quinn post-handshake upgrade path, transports/quic/src/connection/connecting.rs called libp2p_tls::certificate::parse a second time in remote_peer_id and used expect on the result. The repeated wall-clock validity check could reject the now-expired certificate, causing the expect call to terminate any application exposing an affected libp2p-quic listener. This vulnerability is fixed in 0.13.1.

Technical POC Analysis

Bug class: uncaught exception / panic (CWE-248).

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Threat Intelligence Overview

EPSS Score

0.2%

Top 86% exploitable

Threat Intel

1 source

Exploit

POC

Public exploit code exists

Data Quality

5 sources

Confidence: Medium

EUVD

NVD

CVE.org

EPSS GHSA

GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC Yes

EPSS 0.2%

Patch available Yes

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived

Scheduled

Exploitation· derived

Poc

System Exposure· derived

Open

Automatable· derived

Human Impact· derived

Medium

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +41

PoC: +20

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Information Disclosure MEDIUM

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.