Improper Verification of Cryptographic Signature Affecting kibana-8.18-config package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.03% (7th 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-MINIMOSLATEST-KIBANA818CONFIG-15954358
  • published9 Apr 2026
  • disclosed27 Mar 2026

Introduced: 27 Mar 2026

NewCVE-2026-33895  (opens in a new tab)
CWE-347  (opens in a new tab)

How to fix?

There is no fixed version for Minimos:latest kibana-8.18-config.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kibana-8.18-config package and not the kibana-8.18-config package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.4.0, Ed25519 signature verification accepts forged non-canonical signatures where the scalar S is not reduced modulo the group order (S >= L). A valid signature and its S + L variant both verify in forge, while Node.js crypto.verify (OpenSSL-backed) rejects the S + L variant, as defined by the specification. This class of signature malleability has been exploited in practice to bypass authentication and authorization logic (see CVE-2026-25793, CVE-2022-35961). Applications relying on signature uniqueness (i.e., dedup by signature bytes, replay tracking, signed-object canonicalization checks) may be bypassed. Version 1.4.0 patches the issue.

CVSS Base Scores

version 3.1