Skip to content

CVE-2026-27135

Is CVE-2026-27135 real, exploitable, or a false positive? Here's the community verdict.

☆ Watch

signals

public sources

Exploited in wild
Not listed
CISA KEV
Public exploit
None known
Metasploit/EDB/PoC
Base severity
7.5 High
CVSS
Exploitation prob.
0.8%
FIRST EPSS
Weakness
CWE-617
CWE

High CVSS base score, but low real-world exploitation probability (EPSS). Likely less urgent than the score implies.

scanner noise

anonymous, aggregated from real reports · via Denoizr
ScannerFlagged inTurned out noise
Wiz1 scan0%

How often this CVE was flagged by each scanner and how much turned out to be noise (false positives), aggregated anonymously from de-noised reports. Higher noise means the alert is more often not a real risk — verify your exposure.

baseline read

auto · not a community verdict

Real, but low real-world risk

A genuine vulnerability on paper, but EPSS shows little real-world exploitation — the base score may overstate urgency. This is not the same as a false positive.

Based on CVSS · FIRST EPSS

Confirm or dispute →
Affected:Nghttp2

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nghttp2 is an implementation of the Hypertext Transfer Protocol version 2 in C. Prior to version 1.68.1, the nghttp2 library stops reading the incoming data when user facing public API `nghttp2_session_terminate_session` or `nghttp2_session_terminate_session2` is called by the application. They might be called internally by the library when it detects the situation that is subject to connection error. Due to the missing internal state validation, the library keeps reading the rest of the data after one of those APIs is called. Then receiving a malformed frame that causes FRAME_SIZE_ERROR causes assertion failure. nghttp2 v1.68.1 adds missing state validation to avoid assertion failure. No known workarounds are available.

References

NVD MITRE CVE.org

Published

Embed this verdict
TruePositive verdict for CVE-2026-27135
Markdown
[![TruePositive verdict](https://www.truepositive.app/cve/CVE-2026-27135/badge.svg)](https://www.truepositive.app/cve/CVE-2026-27135)
HTML
<a href="https://www.truepositive.app/cve/CVE-2026-27135"><img src="https://www.truepositive.app/cve/CVE-2026-27135/badge.svg" alt="TruePositive verdict for CVE-2026-27135"></a>

Live badge that updates automatically as the community verdict changes.

Community ground truth

Be the first practitioner to weigh in

So far this is only TruePositive's editorial baseline from public sources. Add your real-world verdict below — it becomes the signal the next person triaging this relies on.

🥇 The first 50 practitioners to contribute earn a Founding Contributor badge.

In your experience, is this finding real and exploitable?

awaiting field verdicts
Real, but not a risk here
Not a real issue

Curated baseline: A curated baseline from public sources, shown separately from community verdicts.

No account needed. Anonymous verdicts post as an unverified signal. Log in to make yours verified and earn reputation.

Field notes & remediation

Verdicts are the quick signal. Notes are the evidence and fixes behind them.

  • 0
    Field note · TruePositive EditorialCurated

    This scores high on paper (CVSS 7.5) but the real-world signal is low. It is not in CISA KEV and no public exploit was found, and near-term exploitation looks unlikely (EPSS about 1%). Verify your own exposure before treating it as urgent. It is reachable over the network with no authentication and no user interaction, which is the most dangerous profile. Not an emergency for most teams, but patch it in your normal cycle and check whether the affected component is actually exposed in your setup.

Add a field note or remediationoptional
Note type

What are you adding?

Markdown supported · minimum 20 characters.

Related CVEs

Same weakness: CWE-617.