Improper Input Validation Affecting gitlab-rails-ce-fips-19.2 package, versions <19.2.1-r5


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.47% (39th 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-GITLABRAILSCEFIPS192-18868423
  • published18 Aug 2026
  • disclosed27 Mar 2026

Introduced: 27 Mar 2026

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

How to fix?

Upgrade Chainguard gitlab-rails-ce-fips-19.2 to version 19.2.1-r5 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream gitlab-rails-ce-fips-19.2 package and not the gitlab-rails-ce-fips-19.2 package as distributed by Chainguard. See How to fix? for Chainguard 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, RSASSA PKCS#1 v1.5 signature verification accepts forged signatures for low public exponent keys (e=3). Attackers can forge signatures by stuffing “garbage” bytes within the ASN structure in order to construct a signature that passes verification, enabling Bleichenbacher style forgery. This issue is similar to CVE-2022-24771, but adds bytes in an addition field within the ASN structure, rather than outside of it. Additionally, forge does not validate that signatures include a minimum of 8 bytes of padding as defined by the specification, providing attackers additional space to construct Bleichenbacher forgeries. Version 1.4.0 patches the issue.

CVSS Base Scores

version 3.1