How severe is CVE-2026-111812?

CVE-2026-111812 has a CVSS 3.x base score of 10.0, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2026-111812 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (17th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-111812?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2026-111812 published?

CVE-2026-111812 was published on 2026-10-21 and last updated on 2026-10-22.

CVE-2026-111812

CVE-2026-111812 is a critical-severity vulnerability with a CVSS 3.x base score of 10.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-863.

Key facts

Severity: Critical (CVSS 3.x base score 10.0)
CVSS v4: 7.0
EPSS exploit prediction: 0% (17th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-863
Published: 2026-10-21
Last modified: 2026-10-22

Description

Apache Traffic Server's origin_server_auth plugin lets a client force signing of attacker-chosen AWS request headers under the proxy's own credentials. This issue affects Apache Traffic Server: from 8.0.0 through 8.1.11, from 9.0.0 through 9.2.15, from 10.0.0 through 10.1.4, 10.2.0. Users are recommended to upgrade to version 9.2.16, 10.1.5, or 10.2.1, which fix the issue.

Frequently asked questions

What is CVE-2026-111812?: Apache Traffic Server's origin_server_auth plugin lets a client force signing of attacker-chosen AWS request headers under the proxy's own credentials. This issue affects Apache Traffic Server: from 8.0.0 through 8.1.11, from 9.0.0 through 9.2.15, from 10.0.0 through 10.1.4, 10.2.0. Users are recommended to upgrade to version 9.2.16, 10.1.5, or 10.2.1, which fix the issue.
How severe is CVE-2026-111812?: CVE-2026-111812 has a CVSS 3.x base score of 10.0, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2026-111812 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (17th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-111812?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2026-111812 published?: CVE-2026-111812 was published on 2026-10-21 and last updated on 2026-10-22.

References

https://lists.apache.org/thread/r95dq29ywcd1f4x30snxlqmb12z4s4kc

Other CWE-863 (Incorrect Authorization) vulnerabilities

CVE-2026-90532 — Critical (CVSS 10.0): Adobe Experience Manager is affected by an Incorrect Authorization vulnerability that could result in arbitrary code…
CVE-2026-48383 — Critical (CVSS 10.0): Adobe Experience Manager is affected by an Incorrect Authorization vulnerability that could result in arbitrary code…
CVE-2026-48382 — Critical (CVSS 10.0): Adobe Experience Manager is affected by an Incorrect Authorization vulnerability that could result in arbitrary code…
CVE-2026-75745 — Critical (CVSS 10.0): Adobe Experience Manager Forms JEE is affected by an Incorrect Authorization vulnerability that could result in…
CVE-2026-75723 — Critical (CVSS 10.0): Adobe Campaign Classic (ACC) is affected by an Incorrect Authorization vulnerability that could result in arbitrary…
CVE-2026-69555 — Critical (CVSS 10.0): Incorrect authorization in Azure Arc allows an unauthorized attacker to elevate privileges over a network.

Browse all CWE-863 (Incorrect Authorization) vulnerabilities →