Skip to main content

Szafir Sdk CVE-2026-9058

| EUVDEUVD-2026-31679 CRITICAL
Unnecessary Complexity in Protection Mechanism (Not Using 'Economy of Mechanism') (CWE-637)
2026-05-25 CERT-PL GHSA-7hq7-5m7p-r2pp
9.3
CVSS 4.0 · Vendor: CERT-PL
View

Vulnerability Assessment

Weakness
CWE
Act Now Prioritize within 24-48h. Why: CRITICAL severity.
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 23, 2026

Signature verification bypass in Krajowa Izba Rozliczeniowa (KIR) Szafir SDK before version 463 causes the SDK to return a 'Positively verified' success result (Result/@code 0) even when the signer's certificate trust could not be established (certificateType 'nondetermined'). Consuming applications that rely on this result for authentication accept forged or untrusted-chain signatures as valid, enabling authentication bypass and user impersonation. There is no public exploit identified at time of analysis and EPSS probability is low (0.04%), but CISA's SSVC framework rates the technical impact as total and the flaw as automatable.

Affected VersionsENISA

Szafir SDK 0 <463

Affected Packages

euvd szafir_sdk fix: 463

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Know when Szafir Sdk gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (CERT-PL) PRIMARY 9.3 CRITICAL
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (CERT-PL) · only source for this CVE.

CVSS VectorVendor: CERT-PL

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

3
Patch available
May 26, 2026 - 14:16 EUVD
CVE Published
May 25, 2026 - 13:23 nvd
UNKNOWN (no severity yet)
CVE Published
May 25, 2026 - 13:23 cve.org
CRITICAL 9.3

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

The KIR Szafir SDK signature verification bypass (CVE-2026-9058, CVSS 9.3) allows attackers to forge digital signatures and bypass authentication checks, enabling account takeover and user impersonation. Any organization relying on this SDK for authentication or digital signature verification faces immediate risk of unauthorized access.

Recommended Action

No public exploit has been identified at time of analysis. Within 24 hours, inventory all systems running KIR Szafir SDK versions prior to 463 and assess exposure scope. By day 7, deploy version 463 or later to all affected systems using the vendor's published migration path. Complete functional testing of authentication workflows within 30 days to confirm signature validation is enforcing properly post-upgrade.

Business Impact: Severe
Compensating Controls

Apply vendor patch: KIR Szafir SDK version 463 or later.

Threat Intelligence Overview

EPSS Score
0.0%
Top 89% exploitable
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
Very High
Technical Impact
Total

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +46
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy