CVE-2026-109425: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-5fgm-q74f-6j8f
Share
CVSS 5.3
CWE-1286
Published
Advisory Summary

CVE-2026-109425 is a MODERATE (CVSS 5.3) security vulnerability vulnerability (CWE-1286: Improper Validation of Syntactic Correctness of Input) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product receives input that is expected to be well-formed - i.e., to comply with a certain syntax - but it does not validate or incorrectly validates that the input complies with the syntax.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-109425 at a Glance

CVE Identifier CVE-2026-109425
GHSA Identifier GHSA-5fgm-q74f-6j8f
Severity MODERATE
CVSS v3.1 Base Score 5.3
CWE Classification CWE-1286: Improper Validation of Syntactic Correctness of Input
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 5.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-109425

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

Verify Direct and Transitive Dependencies

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

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-109425, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

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

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-1286: Improper Validation of Syntactic Correctness of Input, where the product receives input that is expected to be well-formed - i.e., to comply with a certain syntax - but it does not validate or incorrectly validates that the input complies with the syntax. In Software, 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

Tink-go (tink-crypto/tink-go) through 2.8.0 contains an input-validation vulnerability where keyset.NewHandleWithNoSecrets() and ReadWithNoSecrets() skip the structural Validate() step before constructing a keyset.Handle, allowing malformed public or no-secret keysets that violate Tink's keyset invariants to be accepted. Attackers can supply a malformed keyset, such as one with an enabled public key lacking a valid primary key or a DESTROYED key with no KeyData, causing inconsistent downstream validation where functions like jwt.JWKSetFromPublicKeysetHandle() process the invalid handle and produce a JWK set, potentially misleading applications that rely on successful handle construction as proof of keyset integrity.

References

NVD — CVE-2026-109425 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-109425
Software Source Repository REPOSITORY
https://github.com/tink-crypto/tink-go/issues/68
www.vulncheck.com/advisories/tink-go-... WEB
https://www.vulncheck.com/advisories/tink-go-keyset-validation-bypass-via-newhandlewithnosecrets

Frequently Asked Questions

What is CVE-2026-109425?
CVE-2026-109425 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-1286: Improper Validation of Syntactic Correctness of Input.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-109425?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-109425?
CVE-2026-109425 has a CVSS v3.1 base score of 5.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N.
What CWE is associated with CVE-2026-109425?
CVE-2026-109425 is classified under CWE-1286: Improper Validation of Syntactic Correctness of Input (The product receives input that is expected to be well-formed - i.e., to comply with a certain syntax - but it does not validate or incorrectly validates that the input complies with the syntax.).
How can I check Maven dependencies for CVE-2026-109425?
Run the dependency tree command: 'mvn dependency:tree'. 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-5fgm-q74f-6j8f",
  "modified" : "2026-10-12T21:31:56Z",
  "published" : "2026-10-12T21:31:56Z",
  "aliases" : [ "CVE-2026-109425" ],
  "details" : "Tink-go (tink-crypto/tink-go) through 2.8.0 contains an input-validation vulnerability where keyset.NewHandleWithNoSecrets() and ReadWithNoSecrets() skip the structural Validate() step before constructing a keyset.Handle, allowing malformed public or no-secret keysets that violate Tink's keyset invariants to be accepted. Attackers can supply a malformed keyset, such as one with an enabled public key lacking a valid primary key or a DESTROYED key with no KeyData, causing inconsistent downstream validation where functions like jwt.JWKSetFromPublicKeysetHandle() process the invalid handle and produce a JWK set, potentially misleading applications that rely on successful handle construction as proof of keyset integrity.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-109425"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/tink-crypto/tink-go/issues/68"
  }, {
    "type" : "WEB",
    "url" : "https://www.vulncheck.com/advisories/tink-go-keyset-validation-bypass-via-newhandlewithnosecrets"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-1286" ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-12T20:17:09Z"
  }
}