# CVE-2026-106036: Improper certificate validation in Szafir


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-c5j4-p43c-gh65

## What is CVE-2026-106036?

CVE-2026-106036 is a medium-severity vulnerability in Krajowa Izba Rozliczeniowa Szafir, published on 29 Oct 2026. 

### Official description

Szafir accepts any client or server certificate without performing certificate and hostname validation, allowing HTTPS connections without authenticating the remote server. An attacker can provide an arbitrary SSL/TLS certificate and cause the application to download an update file from their server.

This issue was fixed in version 2.0 build 708.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2026-106036?


## How do I fix CVE-2026-106036?

No fix has been published for CVE-2026-106036 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-106036 being exploited?

There is no known exploitation of CVE-2026-106036 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-106036 and fix it if it is affected.

What it is: CVE-2026-106036 is a medium-severity vulnerability in Krajowa Izba Rozliczeniowa Szafir, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-106036 in the wild and no public exploit code.

Affected product: Krajowa Izba Rozliczeniowa Szafir. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-106036/ (Markdown: https://insights.sbomify.com/CVE-2026-106036/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-106036
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-106036
- OSV: https://osv.dev/vulnerability/CVE-2026-106036

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-106036/
Summaries are generated and may contain mistakes; the official description above is the record.