GHSA-9gxv-x7rp-r2hc: Gree/jose Gree/jose - "None" Algorithm Treated Vulnerability

CRITICAL
Share
CWE-327 CWE-347
Published
Advisory Summary

GHSA-9gxv-x7rp-r2hc is a CRITICAL gree/jose - "none" algorithm treated vulnerability (CWE-327: Use of a Broken or Risky Cryptographic Algorithm) affecting Gree/jose libraries in the Packagist ecosystem. The issue involves gree/jose - "none" algorithm treated as valid in tokens. Remediation is available by upgrading affected packages to version 2.2.1.

GHSA-9gxv-x7rp-r2hc at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-9gxv-x7rp-r2hc
Severity CRITICAL
CVSS v3.1 Base Score N/A
CWE Classification CWE-327: Use of a Broken or Risky Cryptographic Algorithm
Affected Product Gree/jose
Package Ecosystem Packagist
Published Date
Last Updated

How to Fix GHSA-9gxv-x7rp-r2hc

To remediate this vulnerability, upgrade all affected Gree/jose dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

gree/jose fixed: 2.2.1 
Upgrade gree/jose to 2.2.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for gree/jose

How to Check if You Are Affected

To determine whether your application is affected by GHSA-9gxv-x7rp-r2hc, inspect your project dependencies for Gree/jose:

inspect dependencies for gree/jose

Analyze the terminal output to locate any version of Gree/jose in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.2.1), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-327: Use of a Broken or Risky Cryptographic Algorithm, where the product uses a broken or risky cryptographic algorithm or protocol. In Gree/jose, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

Several widely-used JSON Web Token (JWT) libraries, including node-jsonwebtoken, pyjwt, namshi/jose, php-jwt, and jsjwt, are affected by critical vulnerabilities that could allow attackers to bypass the verification step when using asymmetric keys (RS256, RS384, RS512, ES256, ES384, ES512).

GHSA-9gxv-x7rp-r2hc Affected Gree/jose Versions

1 component(s)
Fixed Versions:
2.2.1
Product / Package Ecosystem Affected Versions Fixed Version
gree/jose
 Packagist
< 2.2.1
2.2.1

References

auth0.com/blog/2015/03/31/cri... WEB
https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries
auth0.com/blog/critical-vulne... WEB
https://auth0.com/blog/critical-vulnerabilities-in-json-web-token-libraries
Gree/jose Source Repository REPOSITORY
https://github.com/FriendsOfPHP/security-advisories/blob/master/gree/jose/2016-08-30.yaml
Gree/jose Source Repository REPOSITORY
https://github.com/nov/jose-php
Gree/jose Source Repository REPOSITORY
https://github.com/nov/jose-php/compare/2.2.0...2.2.1

Frequently Asked Questions

What is GHSA-9gxv-x7rp-r2hc?
GHSA-9gxv-x7rp-r2hc is a security vulnerability in Gree/jose involving gree/jose - "None" Algorithm treated as valid in tokens under CWE-327: Use of a Broken or Risky Cryptographic Algorithm.
Which Gree/jose versions are affected?
Affected versions include releases prior to 2.2.1 across affected packages: gree/jose.
What version fixes GHSA-9gxv-x7rp-r2hc?
Upgrading to 2.2.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is gree/jose affected?
Yes, gree/jose is affected in releases prior to 2.2.1. Upgrade your dependency to 2.2.1 or later.
What CWE is associated with GHSA-9gxv-x7rp-r2hc?
GHSA-9gxv-x7rp-r2hc is classified under CWE-327: Use of a Broken or Risky Cryptographic Algorithm (The product uses a broken or risky cryptographic algorithm or protocol.).
How can I check Packagist dependencies for GHSA-9gxv-x7rp-r2hc?
Run the dependency tree command: 'inspect dependencies for gree/jose'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-9gxv-x7rp-r2hc",
  "modified" : "2026-07-16T18:46:45Z",
  "published" : "2024-05-15T21:47:39Z",
  "aliases" : [ ],
  "summary" : "gree/jose - \"None\" Algorithm treated as valid in tokens",
  "details" : "Several widely-used JSON Web Token (JWT) libraries, including node-jsonwebtoken, pyjwt, namshi/jose, php-jwt, and jsjwt, are affected by critical vulnerabilities that could allow attackers to bypass the verification step when using asymmetric keys (RS256, RS384, RS512, ES256, ES384, ES512).",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "gree/jose"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.2.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries"
  }, {
    "type" : "WEB",
    "url" : "https://auth0.com/blog/critical-vulnerabilities-in-json-web-token-libraries"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/FriendsOfPHP/security-advisories/blob/master/gree/jose/2016-08-30.yaml"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/nov/jose-php"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nov/jose-php/compare/2.2.0...2.2.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-327", "CWE-347" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-05-15T21:47:39Z",
    "nvd_published_at" : null
  }
}