Is this vulnerability remotely exploitable over the internet?

Yes, in typical deployments where Pingora is exposed as an internet-facing reverse proxy and fronts backends that accept HTTP/1.0 and ambiguous framing, an attacker can exploit this remotely by sending crafted HTTP requests.

Does an attacker need authenticated access to exploit this issue?

Not necessarily. If the vulnerable endpoints are publicly accessible and do not require authentication for initial requests, an unauthenticated attacker can attempt smuggling attacks. Authentication requirements will depend on how Pingora and the protected applications are deployed.

What is the safest general fix pattern for this class of bug?

The safest approach is to enforce strict, RFC-compliant HTTP parsing and message length handling at the proxy: - Only accept well-formed HTTP/1.1 requests where possible. - Reject ambiguous or conflicting `Content-Length` and `Transfer-Encoding` combinations. - Ensure front-end and back-end components use consistent, clearly defined parsing rules so that no smuggled data can be interpreted as a separate request downstream.

Severity:

CRITICAL RISK

(9.1)

HTTP Request Smuggling (CWE-444) in Pingora HTTP/1.0 and Transfer-Encoding Parsing

CVE-2026-2835

Published:

Mar 4, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-918

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

Unauthorized Access to Internal Resources via SSRF

May 6, 2026

CWE-863

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Privilege Escalation via Bypassed Access Control

May 6, 2026

Vulnerability Type

Category:

HTTP Request Smuggling

CWE:

CWE-444

Impact:

Proxy Desync Leading to ACL Bypass, Cache Poisoning, and Cross-User Attacks

Severity:

CRITICAL RISK

(9.1)

CVSS Version:

3.1

Vulnerability Type

Category:

HTTP Request Smuggling

CWE:

CWE-444

Impact:

Proxy Desync Leading to ACL Bypass, Cache Poisoning, and Cross-User Attacks

Severity:

CRITICAL RISK

(9.1)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

HTTP Request Smuggling (CWE-444) in Pingora HTTP/1.0 and Transfer-Encoding Parsing

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal