phpwarden
FeaturesComparePricingAdvisoriesBlogDocsChangelogLog in
Log inStart free

Is web-token/jwt-experimental vulnerable?

Composer web-token/jwt-experimental has 2 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

2advisories
0critical
0on CISA KEV
1no fix recorded
CVETitleSeverityCVSSAffectedFixed in
GHSA-6vvh-pxr4-25r7PHP JWT Framework: Chacha20Poly1305 key-encryption algorithm discards the Poly1305 authentication tag, performing no authentication on decrymedium0.0<=4.1.6–
GHSA-jc38-x7x8-2xc8PHP JWT Framework: JWSVerifier uses algorithm from unprotected header, enabling algorithm confusion attackshigh0.0<3.4.10 or >=4.0.0 and <4.0.7 or >=4.1.0 and <4.1.73.4.10, 4.0.7, 4.1.7

Am I affected?

Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# one-time install
pip install phpwarden

# then
phpwarden deps composer.lock

Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command

Install docs   How findings are ranked
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.