basicsecurity.net
Proof, not just disclosure.
Threats / Apache / CVE-2022-24112
CVE-2022-24112 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Apache APISIX vulnerability

Apache APISIX authentication bypass vulnerability enabling remote code execution. Actively exploited in the wild.

Verdict

Today item — known-exploited.

An authentication bypass in Apache APISIX allows unauthenticated attackers to execute arbitrary code on affected systems. The vulnerability has been observed in active exploitation campaigns.

CISA KEV Yes · 2022-08-253EPSS 0.96182 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
679 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-08-25).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.96182 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Apache, APISIX. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-290 Auth Bypass by Spoofing — weakness family: Authentication.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I bypass authentication controls by exploiting the authentication mechanism flaw in APISIX.
Business
Security perimeter is compromised; unauthorized access to API gateway is established.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I execute arbitrary code on the APISIX server following successful authentication bypass.
Business
Complete system compromise occurs; attacker gains code execution privileges on critical infrastructure.
3

Lateral reach — past segmentation narrative 3

Attacker
I establish persistence and move laterally through the network from the compromised gateway.
Business
Downstream systems and data become vulnerable to further compromise and exfiltration.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 679 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by apache (CNA)
  • Named finder/reporter credit (CVE.org)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • Disclosure & credit2
    Catalogued by apacheCNA
    Credited with finding itOriginal discovery by Real World CTF at Chaitin Tech. Reported by Sauercloud.unspecified