CVE Professor
›
Back
CVE-2026-105298

CVE-2026-105298 — CWE-444

NONE CVSS 0 NVD

CVE-2026-105298 is a NONE severity security vulnerability (CWE-444) (CVSS 0.0/10) affecting affected software system. Technical vector analysis shows that an attacker can exploit this flaw remotely over the network without authentication (PR:N) with zero user interaction (UI:N), posing a direct security risk to affected deployments.

📄 Official NVD / MITRE Original Record Text

Summary Before version 0.9.0, Pingora accepted HTTP/2 requests whose Host header differed from the :authority pseudo-header. Request filters, cache keys, and logs that read the request URI (session.req_header().uri) saw the :authority value, but the upstream received the client-supplied Host value. Pingora also accepted :authority values containing userinfo (for example, [email protected]). This violates RFC 9113 Section 8.3.1, which requires an intermediary to use the :authority value for Host and replace any existing Host field. Root cause * HTTP/2 to HTTP/1.1: Host was generated from :authority only when the request had no Host header, so a conflicting client Host was forwarded unchanged. * HTTP/2 to HTTP/2: the client Host header was removed and used to overwrite the upstream :authority, after request filters had already run against the original :authority. * The HTTP/2 server did not compare Host with :authority and did not reject userinfo in the authority. Impact A remote, unauthenticated attacker can send a single HTTP/2 request that the application sees as one host and the upstream receives as another. Where request filters, access controls, or cache keys use the URI authority and the upstream routes by Host, this can lead to: * Cache poisoning: a response from another virtual host is stored under the victim host's cache key and served to other users (this also requires the upstream to serve different content per Host). * Host-based access control bypass: a request approved for one host is served by a different virtual host on the upstream. Deployments that do not accept HTTP/2 from clients, or that do not use the request authority for security or caching decisions, are not affected. Note that Cloudflare CDN customers were unaffected, as internal Pingora services at Cloudflare do not have HTTP/2 clients. Mitigation: * Upgrade to pingora 0.9.0 or later. Pingora now returns 400 Bad Request for HTTP/2 requests whose Host differs from :authority, that contain more than one Host, or whose authority contains userinfo, and keeps the upstream Host or :authority consistent with the request authority. Fix commits: https://github.com/cloudflare/pingora/commit/915590a91811877795531f6ba0927a3138b5cb4b , https://github.com/cloudflare/pingora/commit/ffab8302d08d4292d1924eb8fe84647fd5cb8e76 * If you cannot upgrade: in request_filter, reject HTTP/2 requests that carry a Host header different from the URI authority, or whose authority contains '@'.

Published 20.10.2026
ISO Date 2026-10-20
Source NVD
AI Security Analysis & Remediation
🤖 Generating Deep AI Security Analysis…
Analyzing CVSS vector & CWE weakness structure…

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CVE-2026-105298
CVSS 0/10 · UNKNOWN · 20.10.2026
CWE: CWE-444
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🎯 WHAT IS THIS VULNERABILITY?
Authentication Bypass
Summary: Summary

Before version 0.9.0, Pingora accepted HTTP/2 requests whose Host header differed from the :authority pseudo-header. Request filters, cache keys, and logs that read the request URI (session.req_header().uri) saw the :authority value, but the upstream received the client-supplied Host value. Pingora also accepted :authority values containing userinfo (for example, [email protected]).

⚡ ATTACK CHAIN
1. JWT: change alg to none, remove signature.
2. SQL bypass: ' OR '1'='1'-- in login form.
3. Direct API endpoint access without auth headers.
4. Password reset token prediction or race condition.
5. Credential stuffing with default creds.

🔧 Tools: jwt_tool, Burp Suite, Hydra, sqlmap --forms
🗺️ MITRE ATT&CK: T1078 (Valid Accounts), T1110 (Brute Force)

🌍 REAL WORLD IMPACT

🛡️ REMEDIATION
→ Apply the vendor-released patch immediately.
→ Add MFA, strengthen sessions, implement rate limiting.
→ Add WAF rule, create IDS alert for anomalous traffic.

⚠️ URGENCY
📌 Low priority — routine update sufficient.

────────────────────────────────────────
[Kural Tabanlı Otomatik Güvenlik Analizi]

Target Reconnaissance Queries (FOFA & Shodan)
CVSS Score
0 / 10 · CVSS NONE
Weakness Types (CWE)
CWE-444
References & Advisories (1)
Related CVEs
7.5
CVE-2026-100977
NVIDIA OpenShell for Linux contains a vulnerability in L7 REST policy enforcement where a local attacker with
6.4
CVE-2026-100981
NVIDIA OpenShell for Linux contains a vulnerability in its layer-7 REST proxy where a sandboxed actor could by
6.3
CVE-2026-119348
Next.js is a React framework for building full-stack web applications. Prior to 15.5.29 and 16.4.5, self-hoste
4.8
CVE-2026-123318
In JetBrains Ktor before 3.6.1 hTTP request smuggling was possible in the CIO engine
7.5
CVE-2026-103866
Inconsistent interpretation of HTTP requests ('HTTP Request/Response smuggling') vulnerability in Apache Sling
2.9
CVE-2026-55458
Caddy is an extensible server platform that uses TLS by default. Prior to 2.11.5, the reverse proxy's finalize