CVE-2026-9058

Published: Mag 25, 2026 Last Modified: Mag 25, 2026
ExploitDB:
Other exploit source:
Google Dorks:
CRITICAL 9,3
Source: [email protected]
Attack Vector: network
Attack Complexity: low
Privileges Required: none
User Interaction: none
Confidentiality: N/A
Integrity: N/A
Availability: N/A

Description

AI Translation Available

Szafir SDK returns a success status code from the cryptographic digital signature verification process (i.e. /VerifyingTaskItem/Signature/VerificationResult/Result/@code == 0, 'Positively verified') even when the trust status of the signer's certificate could not be established (i.e. /VerifyingTaskItem/Signature/VerificationResult/SigningCertificate/@certificateType == 'nondetermined'). This causes consuming applications to incorrectly treat the signature as valid despite an unverified certificate chain, enabling authentication bypass and user impersonation.

This issue was fixed in version 463.

EPSS (Exploit Prediction Scoring System)

Trend Analysis

EPSS (Exploit Prediction Scoring System)

Prevede la probabilità di sfruttamento basata su intelligence sulle minacce e sulle caratteristiche della vulnerabilità.

EPSS Score
0,0004
Percentile
0,1th
Updated

Single Data Point

Only one EPSS measurement is available for this CVE. Trend analysis requires multiple data points over time.

393

Return of Wrong Status Code

Draft
Abstraction: Base Structure: Simple
Common Consequences
Security Scopes Affected:
Integrity Other
Potential Impacts:
Unexpected State Alter Execution Logic
Applicable Platforms
All platforms may be affected
View CWE Details
637

Unnecessary Complexity in Protection Mechanism (Not Using 'Economy of Mechanism')

Draft
Abstraction: Class Structure: Simple
Common Consequences
Security Scopes Affected:
Other
Potential Impacts:
Other
Applicable Platforms
All platforms may be affected
View CWE Details
https://cert.pl/posts/2026/05/CVE-2026-9058
https://cert.pl/posts/2026/05/CVE-2026-9058
https://www.elektronicznypodpis.pl/
https://www.elektronicznypodpis.pl/