VulertSecurity VulertSecurity

Vulnerability Database · Bitnami · Package report

apisix: vulnerability history, versions and safety

apisix is a package in the Bitnami ecosystem. Vulert records 36 vulnerabilities for it across 31 affected ranges, from Mar 2024 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
36 vulnerabilities recorded C2 H11 M16 L6 U1
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
27 in the last 12 months

Most recent disclosure 09 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all apisix vulnerabilities

Vulert verdict on apisix i

Updated on 23 Oct 2026

Careful: 2 of the 36 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 36 vulnerabilities on record across 2 years, 27 in the last year.

What to do: Plan around the 2 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 36 over 2 years · 27 in the last year i
  • Latest disclosure 09 Oct 2026 i
  • Highest CVSS n/a i
  • With no published fix 2 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
from 3.17.0 up to 3.19.0 (exclusive) 2
from 1.3.0 up to 3.19.0 (exclusive) 1
from 2.14.1 up to 3.19.0 (exclusive) 1
from 3.12.0 up to 3.19.0 (exclusive) 1
from 3.17.0 up to 3.18.0 (exclusive) 2
from 3.11.0 up to 3.18.0 (exclusive) 1
from 2.12.0 up to 3.18.0 (exclusive) 1
from 2.11.0 up to 3.18.0 (exclusive) 1
from 3.0.0 up to 3.17.0 (exclusive) 4
from 2.12.0 up to 3.17.0 (exclusive) 1
from 2.2.0 up to 3.17.0 (exclusive) 1
from 1.2.0 up to 3.17.0 (exclusive) 1
from 2.3.0 up to 3.17.0 (exclusive) 1
from 2.14.1 up to 3.17.0 (exclusive) 1
from 3.8.0 up to 3.17.0 (exclusive) 1
from 2.12.0 up to 3.16.0 (exclusive) 1
from 0.7.0 up to 3.16.0 (exclusive) 1
from 2.99.0 up to 3.16.0 (exclusive) 1
from 1.0.0 up to 3.14.0 (exclusive) 1
up to 3.12.0 (exclusive) 1
from 3.8.0 up to 3.9.1 (exclusive) 1
from 0.2.0 up to 3.9.0 (exclusive) 1
from 2.3.0 up to 3.7.0 (exclusive) 1
up to 3.6.1 (exclusive) 1
up to 2.13.1 (exclusive) 1
up to 2.13.0 (exclusive) 1
up to 2.10.4 (exclusive) 1
up to 2.10.2 (exclusive) 1
from 1.2.0 up to 1.5.1 (exclusive) 1
from 3.11.0 onwards, no fix published yet 1
from 3.5.0 onwards, no fix published yet 1

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 7
  • 2025 3
  • 2026 26

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 27 of the 36 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for apisix

The 5 most severe of 36 vulnerabilities recorded for this package

Search all 36 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-13945: Apache APISIX Admin API Access IP Restriction Bypass N/A medium 1.5.1 06 Mar 2024
CVE-2026-94276: Apache APISIX Openid-Connect Introspection Validation Issue N/A medium 3.19.0 09 Oct 2026
CVE-2026-75020: Apache APISIX ldap-auth Plugin Cross-Subtree Identity Impersonation Vulnerability N/A high 3.18.0 01 Sep 2026
CVE-2026-74848: Apache APISIX Cross-user Response Poisoning Vulnerability N/A high 3.18.0 01 Sep 2026
CVE-2026-75005: Apache APISIX Unauthenticated CPU-exhaustion DoS Vulnerability N/A high 3.18.0 31 Aug 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About apisix

Is apisix safe to use?

Vulert records 36 vulnerabilities for apisix in Bitnami: 2 critical, 11 high, 16 medium and 6 low, plus 1 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does apisix have?

36 vulnerabilities are recorded for apisix in the Bitnami ecosystem: 2 critical, 11 high, 16 medium and 6 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new apisix vulnerabilities disclosed?

27 vulnerabilities were recorded for apisix in the last 12 months, and the oldest entry in this database dates to 06 Mar 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of apisix are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor apisix for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the apisix version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.