Vulnerability Database · Packagist · Package report

auth0/auth0-php: vulnerability history, versions and safety

auth0/auth0-php is a package in the Packagist ecosystem. Vulert records 5 vulnerabilities for it across 101 releases, from May 2025 to Apr 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded C2 H1 M1 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 01 Apr 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on auth0/auth0-php i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 01 Apr 2026. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 5 vulnerabilities on record across 1 year, 2 in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 5 over 1 year · 2 in the last year i
  • Latest disclosure 01 Apr 2026 i
  • Highest CVSS 9.3 i
  • With no published fix 0 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

Every version Vulert holds for auth0/auth0-php, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
8.18.0 H1 Yes Details →
8.17.0 H1 M1 Yes Details →
8.16.0 H1 M1 L1 Yes Details →
8.15.0 H1 M1 L1 Yes Details →
8.14.0 H1 M1 L1 Yes Details →
8.13.0 C1 H1 M1 L1 Yes Details →
8.12.0 C1 H1 M1 L1 Yes Details →
8.11.1 C1 H1 M1 L1 Yes Details →
8.11.0 C1 H1 M1 L1 Yes Details →
8.10.0 C1 H1 M1 L1 Yes Details →
8.9.3 C1 H1 M1 L1 Yes Details →
8.9.1 C1 H1 M1 L1 Yes Details →
8.9.0 C1 H1 M1 L1 Yes Details →
8.8.0 C1 H1 M1 L1 Yes Details →
8.7.1 C1 H1 M1 L1 Yes Details →
8.7.0 C1 H1 M1 L1 Yes Details →
8.6.0 C1 H1 M1 L1 Yes Details →
8.5.0 C1 H1 M1 L1 Yes Details →
8.4.0 C1 H1 M1 L1 Yes Details →
8.3.8 C1 H1 M1 L1 Yes Details →
8.3.7 C1 H1 M1 L1 Yes Details →
8.3.6 C1 H1 M1 L1 Yes Details →
8.3.5 C1 H1 M1 L1 Yes Details →
8.3.4 C1 H1 M1 L1 Yes Details →
8.3.3 C1 H1 M1 L1 Yes Details →
8.3.2 C1 H1 M1 L1 Yes Details →
8.3.1 C1 H1 M1 L1 Yes Details →
8.3.0 C2 H1 M1 L1 Yes Details →
8.2.1 C2 H1 M1 L1 Yes Details →
8.2.0 C2 H1 M1 L1 Yes Details →
8.1.0 C2 H1 M1 L1 Yes Details →
8.0.6 C2 H1 M1 L1 Yes Details →
8.0.5 C2 H1 M1 L1 Yes Details →
8.0.4 C2 H1 M1 L1 Yes Details →
8.0.3 C2 H1 M1 L1 Yes Details →
8.0.2 C2 H1 M1 L1 Yes Details →
8.0.1 C2 H1 M1 L1 Yes Details →
8.0.0 C2 H1 M1 L1 Yes Details →
8.0.0-BETA3 C2 L1 Yes Details →
8.0.0-BETA2 C1 L1 Yes Details →
8.0.0-BETA1 C1 L1 Yes Details →
7.9.2 L1 Yes Details →
7.9.1 L1 Yes Details →
7.9.0 L1 Yes Details →
7.8.0 L1 Yes Details →
7.7.0 L1 Yes Details →
7.6.2 L1 Yes Details →
7.6.1 L1 Yes Details →
7.6.0 L1 Yes Details →
7.5.0 L1 Yes Details →
7.4.0 L1 Yes Details →
7.3.0 L1 Yes Details →
7.2.0 L1 Yes Details →
7.1.0 L1 Yes Details →
7.0.0 L1 Yes Details →
6.0.0-alpha.2 L1 Yes Details →
6.0.0-alpha.1 L1 Yes Details →
5.7.0 L1 Yes Details →
5.6.0 L1 Yes Details →
5.5.1 L1 Yes Details →
5.5.0 L1 Yes Details →
5.4.0 L1 Yes Details →
5.3.2 L1 Yes Details →
5.3.1 L1 Yes Details →
5.3.0 L1 Yes Details →
5.2.0 L1 Yes Details →
5.1.1 L1 Yes Details →
5.1.0 L1 Yes Details →
5.0.6 L1 Yes Details →
5.0.5 L1 Yes Details →
5.0.4 L1 Yes Details →
5.0.3 L1 Yes Details →
5.0.2 L1 Yes Details →
5.0.1 L1 Yes Details →
5.0.0 L1 Yes Details →
4.0.13 L1 Yes Details →
4.0.12 L1 Yes Details →
4.0.11 L1 Yes Details →
4.0.10 L1 Yes Details →
4.0.9 L1 Yes Details →
4.0.8 L1 Yes Details →
4.0.7 L1 Yes Details →
4.0.6 L1 Yes Details →
4.0.5 L1 Yes Details →
4.0.4 L1 Yes Details →
4.0.3 L1 Yes Details →
4.0.2 L1 Yes Details →
4.0.1 L1 Yes Details →
4.0.0 L1 Yes Details →
3.4.3 L1 Yes Details →
3.4.2 L1 Yes Details →
3.4.1 L1 Yes Details →
3.4.0 L1 Yes Details →
3.3.7 L1 Yes Details →
3.3.6 L1 Yes Details →
3.3.5 L1 Yes Details →
3.3.4 L1 Yes Details →
3.3.3 L1 Yes Details →
3.3.2 L1 Yes Details →
3.3.1 L1 Yes Details →
3.3.0 L1 Yes Details →

Newest 101 of 101 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 4
  • 2026 1

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

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 auth0/auth0-php

Is auth0/auth0-php safe to use?

Vulert records 5 vulnerabilities for auth0/auth0-php in Packagist: 2 critical, 1 high, 1 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does auth0/auth0-php have?

5 vulnerabilities are recorded for auth0/auth0-php in the Packagist ecosystem: 2 critical, 1 high, 1 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new auth0/auth0-php vulnerabilities disclosed?

2 vulnerabilities were recorded for auth0/auth0-php in the last 12 months, and the oldest entry in this database dates to 16 May 2025. 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 auth0/auth0-php 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 auth0/auth0-php for upcoming vulnerabilities?

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