Improper Verification of Cryptographic Signature Affecting wazuh-manager package, versions <4.14.5-r5


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.13% (3rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-WAZUHMANAGER-17690202
  • published30 Jun 2026
  • disclosed28 May 2026

Introduced: 28 May 2026

CVE-2026-48523  (opens in a new tab)
CWE-347  (opens in a new tab)

How to fix?

Upgrade Chainguard wazuh-manager to version 4.14.5-r5 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream wazuh-manager package and not the wazuh-manager package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

PyJWT is a JSON Web Token implementation in Python. From 2.9.0 to 2.12.1, there is a verifier-side algorithm allow-list bypass when jwt.decode() or jwt.decode_complete() are called with a PyJWK key. The token header alg is checked against the caller-supplied algorithms allow-list, but signature verification is performed with the algorithm bound to the PyJWK object instead of the header algorithm. An attacker who controls a registered JWK/JWKS private key can sign with a disallowed algorithm, advertise an allowed algorithm in the JWT header, and still be accepted. The issue affects the documented PyJWKClient.get_signing_key_from_jwt(...) flow. This vulnerability is fixed in 2.13.0.

CVSS Base Scores

version 3.1