GHSA-88q6-jcjg-hvmw: Github.com/beatt83/jose swift Jose-swift Has JWT Signature Verification Vulnerability

HIGH
CWE-327
Published
Advisory Summary

GHSA-88q6-jcjg-hvmw is a HIGH jose-swift has jwt signature verification vulnerability (CWE-327: Use of a Broken or Risky Cryptographic Algorithm) affecting Github.com/beatt83/jose swift libraries in the SwiftURL ecosystem. The issue involves jose-swift has jwt signature verification bypass via none algorithm. Remediation is available by upgrading affected packages to version 6.0.2.

GHSA-88q6-jcjg-hvmw at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-88q6-jcjg-hvmw
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-327: Use of a Broken or Risky Cryptographic Algorithm
Affected Product Github.com/beatt83/jose swift
Package Ecosystem SwiftURL
Published Date
Last Updated

How to Fix GHSA-88q6-jcjg-hvmw

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

github.com/beatt83/jose-swift fixed: 6.0.2
Upgrade github.com/beatt83/jose-swift to 6.0.2
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 github.com/beatt83/jose-swift

How to Check if You Are Affected

To determine whether your application is affected by GHSA-88q6-jcjg-hvmw, inspect your project dependencies for Github.com/beatt83/jose swift:

inspect dependencies for github.com/beatt83/jose-swift

Analyze the terminal output to locate any version of Github.com/beatt83/jose swift in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 6.0.2), 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 Github.com/beatt83/jose swift, 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

### Summary An authentication bypass vulnerability allows any unauthenticated attacker to forge arbitrary JWT tokens by setting "alg": "none" in the token header. The library's verification functions immediately return `true` for such tokens without performing any cryptographic verification, enabling complete impersonation of any user and privilege escalation. ### Details The vulnerability exists in Sources/JSONWebSignature/JWS+Verify.swift at lines 34-37: ``` public func verify<Key>(key: Key?) throws -> Bool { guard SigningAlgorithm.none != protectedHeader.algorithm else { return true // <-- Vulnerability: returns true without verification } ``` When the JWT header contains "alg": "none", the verify() method returns true immediately without: 1. Checking if the signature is empty or present 2. Validating the token against any key 3. Requiring explicit opt-in from the caller The SigningAlgorithm enum in Sources/JSONWebAlgorithms/Signatures/SigningAlgorithm.swift:72 explicitly includes case none = "none" as a valid algorithm. All verification methods are affected: - JWS.verify(key:) - Instance method - JWS.verify(jwsString:payload:key:) - Static method - JWT.verify(jwtString:senderKey:) - High-level API ### PoC 1. Create a forged JWT with modified claims: // Forged header with alg:none let header = #"{"alg":"none","typ":"JWT"}"# // Attacker's payload with escalated privileges let payload = #"{"sub":"user123","admin":true}"# // Base64URL encode and concatenate with empty signature let forgedToken = base64url(header) + "." + base64url(payload) + "." // Result: eyJhbGciOiJub25lIiwidHlwIjoiSldUIn0.eyJzdWIiOiJ1c2VyMTIzIiwiYWRtaW4iOnRydWV9. 2. Verify the forged token passes verification: let jws = try JWS(jwsString: forgedToken) let isValid = try jws.verify(key: legitimateSecretKey) // Returns TRUE ### Impact This is an authentication bypass vulnerability. Who is impacted: Any application using jose-swift for JWT verification is vulnerable. An attacker can: - Forge identity: Create tokens claiming to be any user - Escalate privileges: Add admin/superuser claims to gain unauthorized access - Bypass authentication entirely: Access protected resources without valid credentials - Modify any claim: Change expiration, audience, issuer, or any custom claims The attack requires no knowledge of the signing key and works against all signature algorithms (HS256, RS256, ES256, etc.) since the attacker simply bypasses signature verification entirely. ### Credits Reported by Louis Nyffenegger - https://pentesterlab.com/

GHSA-88q6-jcjg-hvmw Affected Github.com/beatt83/jose swift Versions

1 component(s)
Fixed Versions:
6.0.2
Product / Package Ecosystem Affected Versions Fixed Version
github.com/beatt83/jose-swift
SwiftURL
< 6.0.2
6.0.2

References

Frequently Asked Questions

What is GHSA-88q6-jcjg-hvmw?
GHSA-88q6-jcjg-hvmw is a security vulnerability in Github.com/beatt83/jose swift involving jose-swift has JWT Signature Verification Bypass via None Algorithm under CWE-327: Use of a Broken or Risky Cryptographic Algorithm.
Which Github.com/beatt83/jose swift versions are affected?
Affected versions include releases prior to 6.0.2 across affected packages: github.com/beatt83/jose-swift.
What version fixes GHSA-88q6-jcjg-hvmw?
Upgrading to 6.0.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/beatt83/jose-swift affected?
Yes, github.com/beatt83/jose-swift is affected in releases prior to 6.0.2. Upgrade your dependency to 6.0.2 or later.
What CWE is associated with GHSA-88q6-jcjg-hvmw?
GHSA-88q6-jcjg-hvmw 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 SwiftURL dependencies for GHSA-88q6-jcjg-hvmw?
Run the dependency tree command: 'inspect dependencies for github.com/beatt83/jose-swift'. 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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-88q6-jcjg-hvmw",
  "modified" : "2026-03-25T20:10:46Z",
  "published" : "2026-01-09T19:39:30Z",
  "aliases" : [ ],
  "summary" : "jose-swift has JWT Signature Verification Bypass via None Algorithm",
  "details" : "### Summary\nAn authentication bypass vulnerability allows any unauthenticated attacker to forge arbitrary JWT tokens by setting \"alg\": \"none\" in the token header. The library's verification functions immediately return `true` for such tokens without performing any cryptographic verification, enabling complete impersonation of any user and privilege escalation.\n\n### Details\n  The vulnerability exists in Sources/JSONWebSignature/JWS+Verify.swift at lines 34-37:\n\n```\n  public func verify<Key>(key: Key?) throws -> Bool {\n      guard SigningAlgorithm.none != protectedHeader.algorithm else {\n          return true  // <-- Vulnerability: returns true without verification\n      }\n```\n  When the JWT header contains \"alg\": \"none\", the verify() method returns true immediately without:\n  1. Checking if the signature is empty or present\n  2. Validating the token against any key\n  3. Requiring explicit opt-in from the caller\n  \n\n The SigningAlgorithm enum in Sources/JSONWebAlgorithms/Signatures/SigningAlgorithm.swift:72 explicitly includes case none = \"none\" as a valid algorithm.\n\n  All verification methods are affected:\n  - JWS.verify(key:) - Instance method\n  - JWS.verify(jwsString:payload:key:) - Static method\n  - JWT.verify(jwtString:senderKey:) - High-level API\n\n### PoC\n\n  1. Create a forged JWT with modified claims:\n  // Forged header with alg:none\n  let header = #\"{\"alg\":\"none\",\"typ\":\"JWT\"}\"#\n\n  // Attacker's payload with escalated privileges\n  let payload = #\"{\"sub\":\"user123\",\"admin\":true}\"#\n\n  // Base64URL encode and concatenate with empty signature\n  let forgedToken = base64url(header) + \".\" + base64url(payload) + \".\"\n  // Result: eyJhbGciOiJub25lIiwidHlwIjoiSldUIn0.eyJzdWIiOiJ1c2VyMTIzIiwiYWRtaW4iOnRydWV9.\n\n  2. Verify the forged token passes verification:\n  let jws = try JWS(jwsString: forgedToken)\n  let isValid = try jws.verify(key: legitimateSecretKey)  // Returns TRUE\n\n\n### Impact\n\n  This is an authentication bypass vulnerability.   Who is impacted: Any application using jose-swift for JWT verification is vulnerable. An attacker can:\n\n  - Forge identity: Create tokens claiming to be any user\n  - Escalate privileges: Add admin/superuser claims to gain unauthorized access\n  - Bypass authentication entirely: Access protected resources without valid credentials\n  - Modify any claim: Change expiration, audience, issuer, or any custom claims\n\n  The attack requires no knowledge of the signing key and works against all signature algorithms (HS256, RS256, ES256, etc.) since the attacker simply bypasses signature verification entirely.\n\n### Credits\nReported by Louis Nyffenegger - https://pentesterlab.com/",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:P"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "SwiftURL",
      "name" : "github.com/beatt83/jose-swift"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "6.0.2"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 6.0.1"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/beatt83/jose-swift/security/advisories/GHSA-88q6-jcjg-hvmw"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/beatt83/jose-swift/pull/62"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/beatt83/jose-swift/commit/13e5ae6f23ef1487b0dad72540eff414272bd7ca"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/beatt83/jose-swift"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/beatt83/jose-swift/releases/tag/6.0.2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-327" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-01-09T19:39:30Z",
    "nvd_published_at" : null
  }
}