CVE-2022-25763 [High] | Input Validation Bypass in Traffic Server

Improper Input Validation vulnerability in HTTP/2 request validation of Apache Traffic Server allows an attacker to create smuggle or cache poison attacks. This issue affects Apache Traffic Server 8.0.0 to 9.1.2.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	1.09%	1.58%	+0.50%
2	2026-05-29	0.32%	1.09%	+0.77%
3	2026-05-26	—	0.32%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

1.09%

1.58%

+0.50%

2026-05-29

0.32%

1.09%

+0.77%

2026-05-26

—

0.32%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.5	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:N) Service keeps running; no real outage angle.	3.9	3.6	[email protected]
6.8	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:N) Service keeps running; no real outage angle.	1.6	5.2	134c704f-9b21-4f2e-91b3-4a467353bcc0

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.5

3.1

HIGH

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

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N): Service keeps running; no real outage angle.

3.9

3.6

[email protected]

6.8

3.1

MEDIUM

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N): Service keeps running; no real outage angle.

1.6

5.2

134c704f-9b21-4f2e-91b3-4a467353bcc0

OS Trackers for CVE-2022-25763

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-25763 not yet assigned priority: Debian including 1 source packages (trafficserver), 3 status rows across 3 suites (bookworm, bullseye, sid): resolved 3.	https://security-tracker.debian.org/tracker/CVE-2022-25763
`ubuntu`	medium	CVE-2022-25763 medium priority: Ubuntu including 1 source packages (trafficserver), 13 status rows across 13 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): not-affected 6, needs-triage 4, ignored 2, released 1.	https://ubuntu.com/security/CVE-2022-25763

Affected software / configurations for CVE-2022-25763

Vendor	Product	Version	Raw CPE
apache	traffic_server	>= 8.0.0, < 8.1.5	cpe:2.3:a:apache:traffic_server::::::::
apache	traffic_server	>= 9.0.0, < 9.1.3	cpe:2.3:a:apache:traffic_server::::::::
debian	debian_linux	11.0	cpe:2.3:o:debian:debian_linux:11.0:::::::*
fedoraproject	fedora	35	cpe:2.3:o:fedoraproject:fedora:35:::::::*
fedoraproject	fedora	36	cpe:2.3:o:fedoraproject:fedora:36:::::::*

References for CVE-2022-25763

URL	Tags
https://lists.apache.org/thread/rc64lwbdgrkv674koc3zl1sljr9vwg21	Mailing List Vendor Advisory
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/CJ67IWD5PRJUOIYIDJRUG3UMS2UF4X4J/	Mailing List Third Party Advisory
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZCSBQBYPOZSWS5LCOAQ6LJLRLXFIAW5A/	Mailing List Third Party Advisory
https://www.debian.org/security/2022/dsa-5206	Third Party Advisory

URL

CVE-2022-25763 | Improper input validation on HTTP/2 headers

Exploit prediction scoring system (EPSS) score for CVE-2022-25763

Common vulnerability scoring system (CVSS) metrics for CVE-2022-25763

Weakness enumeration for CVE-2022-25763

OS Trackers for CVE-2022-25763

Affected software / configurations for CVE-2022-25763

References for CVE-2022-25763