CVE-2026-9058
Deferred Deferred - Pending Action

Szafir SDK Signature Verification Bypass via Unverified Certificate

Vulnerability report for CVE-2026-9058, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-05-25

Last updated on: 2026-07-23

Assigner: CERT.PL

Description

For untrusted certificates that contain the "Authority Information Access - caIssuers URI" extension, Szafir SDK will automatically download the parent CA certificate from the specified URL and will import it to its trust store as a "nonqualified" certificate. In such a case, Szafir SDK returns a success status code of 0 ("Positively verified") upon successful cryptographic verification and a certificate status of "nonqualified". For other types of untrusted certificates, Szafir SDK returns a success status code of 0 ("Positively verified") upon successful cryptographic verification and a certificate status of "nondetermined". This may lead integrating applications to incorrectly treat the digital signature as valid despite an untrusted certificate chain. This flaw enables authentication bypass and user impersonation: (1) in use-cases other than qualified certificate authentication, or (2) if the qualified certificate authentication use-case is not correctly implemented by the integrating application. This issue was fixed in version 1.8.463.2.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-05-25
Last Modified
2026-07-23
Generated
2026-07-26
AI Q&A
2026-05-26
EPSS Evaluated
2026-07-24
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
szafir szafir_sdk 463

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-295 The product does not validate, or incorrectly validates, a certificate.
CWE-393 A function or operation returns an incorrect return value or status code that does not indicate the true result of execution, causing the product to modify its behavior based on the incorrect result.
CWE-637 The product uses a more complex mechanism than necessary, which could lead to resultant weaknesses when the mechanism is not correctly understood, modeled, configured, implemented, or used.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The vulnerability in the Szafir SDK causes it to return a success status code from the digital signature verification process even when the trust status of the signer's certificate cannot be established.

Specifically, the SDK indicates a signature is "Positively verified" (code == 0) despite the certificate type being "nondetermined", meaning the certificate chain is unverified.

As a result, applications using this SDK may incorrectly treat signatures as valid, enabling attackers to bypass authentication and impersonate users.

Impact Analysis

This vulnerability can lead to authentication bypass, allowing attackers to impersonate legitimate users.

Because the SDK incorrectly validates digital signatures with unverified certificates, malicious actors could gain unauthorized access to systems or data.

Compliance Impact

This vulnerability causes the Szafir SDK to incorrectly indicate that a digital signature verification was successful even when the signer's certificate trust status is undetermined. As a result, consuming applications may treat unverified signatures as valid, enabling authentication bypass and user impersonation.

Such authentication bypass and user impersonation risks can lead to violations of security requirements in common standards and regulations like GDPR and HIPAA, which mandate strong authentication and data integrity controls to protect personal and sensitive information.

Therefore, this vulnerability could negatively impact compliance by undermining the trustworthiness of digital signatures used for authentication and data validation.

Mitigation Strategies

The vulnerability is fixed in Szafir SDK version 463. Immediate mitigation should include upgrading to version 463 or later to ensure the cryptographic digital signature verification process correctly validates the trust status of the signer's certificate.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-9058. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart