CVE Professor — Güvenlik Açığı Takip & Analiz
›
CVE-2026-105299

CWE-444

YÜKSEK CVSS 8.7 ⚡ EPSS 0.4% NVD

Summary Before version 0.9.0, the HTTP/1 upstream path in pingora-proxy passed the downstream request through upstream_request_filter and wrote it to the upstream without removing the client's Connection header, other hop-by-hop headers, or the headers Connection nominated, although RFC 9110 Section 7.6.1 requires intermediaries to remove them. The HTTP/2 upstream path already removed Connection and related HTTP/1-specific headers. A client could therefore nominate a header that the application adds in upstream_request_filter (for example, Connection: keep-alive, X-Forwarded-For). A downstream HTTP/1 intermediary that honors Connection would then strip the Pingora-added header before it reached the origin. Impact Specifically affects chained deployments where an HTTP/1 intermediary between Pingora and the origin processes Connection nominations (for example, Go's net/http/httputil.ReverseProxy) and the origin trusts headers added by that intermediary (for example, X-Forwarded-For for IP-based authorization). A remote, unauthenticated attacker can have those headers removed, potentially bypassing authorization. The reporter demonstrated access to an IP-restricted endpoint using X-Forwarded-For for IP validation on the origin. This is the same class of issue as CVE-2022-31813 in Apache HTTP Server. Note that Cloudflare CDN customers were unaffected, as no such chained deployment as described above exists with internal Pingora services, and Connection headers are sanitized before arriving at Pingora gateways. Mitigation: * Upgrade to pingora 0.9.0 or later. By default, Pingora now removes hop-by-hop and Connection-nominated headers from upstream requests, and rejects requests whose Connection header nominates Host, X-Forwarded-For, X-Forwarded-Host, X-Forwarded-Proto, or a pseudo-header. This is controlled by PeerOptions::http_upstream_request_policy (HttpUpstreamRequestPolicy). Fix commits: https://github.com/cloudflare/pingora/commit/28c18e6b6b04dd0bd937234e5950049e6d74cded , https://github.com/cloudflare/pingora/commit/ca23f1668eca8e78be7ba62ef0edbd458b40eeee * Do not use HttpUpstreamRequestPolicy::preserve() if the origin relies on headers added by Pingora; it restores the old passthrough behavior. * If you cannot upgrade: in upstream_request_filter, remove the Connection header and every header it nominates before adding trusted headers.

Yayınlanma 20.10.2026
ISO Tarih 2026-10-20
CVSS Sürüm v3.1
Kaynak NVD
CVSS v3.1 Metrikleri
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
Attack Vector Network AV:N
Attack Complexity High AC:H
Privileges Req. None PR:N
User Interaction None UI:N
Scope Changed S:C
Confidentiality High C:H
Integrity High I:H
Availability None A:N
EPSS — Exploit Olasılık Skoru
0.4%
30 günlük olasılık
Tüm CVElerin 37. yüzdeliğinde — Bu açığın istismar edilme ihtimali çoğu CVEden yüksek.
AI Güvenlik Analizi

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CVE-2026-105299
CVSS 8.7/10 · YÜKSEK · 20.10.2026
CWE: CWE-444
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🎯 AÇIK NEDİR?
Authentication Bypass
Açıklama: Summary

Before version 0.9.0, the HTTP/1 upstream path in pingora-proxy passed the downstream request through upstream_request_filter and wrote it to the upstream without removing the client's Connection header, other hop-by-hop headers, or the headers Connection nominated, although RFC 9110 Section 7.6.1 requires intermediaries to remove them. The HTTP/2 upstream path already removed Connec…

⚡ SALDIRI ZİNCİRİ
Saldırı adımları:
1. JWT token manipulation: alg=none ile imzasız token oluşturulur.
2. SQL auth bypass: ' OR '1'='1'-- ile login formu geçilir.
3. Session fixation: önceden bilinen session ID zorlanır.
4. Admin API direct call: kimlik doğrulama gerektirmeyen endpoint bulunur.
5. Default credential spray: admin/admin, admin/password123.

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

🌍 GERÇEK DÜNYA ETKİSİ
Tüm gizli veriler okunabilir/çalınabilir; sistem verileri değiştirilebilir/silinebilir; diğer sistemlere pivot mümkün.

🛡️ ÇÖZÜM VE MİTİGASYON
→ Üretici tarafından yayınlanan yamayı uygula.
→ MFA ekle, session yönetimini güçlendir, rate limiting uygula.
→ Yama öncesi: servis erişimini VPN arkasına al veya IP whitelist uygula.
→ WAF kuralı ekle, anormal trafik için IDS alert oluştur.

⚠️ ACİLİYET
⚠️ Bu hafta (7 gün) — Yüksek risk, anonim uzaktan.

────────────────────────────────────────
[Kural Tabanlı Analiz] [💡 config.json dosyasına ai_key (Claude: sk-ant-... veya Groq: gsk_...) ekleyerek gerçek AI analizi kullanabilirsiniz]

[⚠️ AI key mevcut ancak istek başarısız — kural tabanlı analiz kullanıldı]

Hedef Keşif Sorguları
CVSS Skoru
8.7 / 10 · CVSS YÜKSEK
Zayıflık Türleri (CWE)
CWE-444
Referanslar (1)
İlgili CVE'ler
10.0
CVE-2026-88773
Inconsistent interpretation of HTTP requests ('HTTP Request/Response smuggling') vulnerability in Citrix NetSc
9.8
CVE-2026-92238
A maliciously constructed mail header could lead to multiple fields being parsed as one, or potential memory s
9.4
CVE-2026-88092
Inconsistent interpretation of http requests ('http request/response smuggling') in ASP.NET Core allows an una
9.3
CVE-2026-111816
Apache Traffic Server forwarded a malformed 302 response that should have been rejected as a parse error, beca
9.3
CVE-2026-111809
Apache Traffic Server allows request smuggling via HEAD requests that carry Content-Length or Transfer-Encodin