Vulnerability in ASE/Kalkitech ASE2000 V2 Communication Test Set (CVE-2026-90647)
Summary
Vulnerability in ASE/Kalkitech ASE2000 V2 Communication Test Set (CVE-2026-90647). Confidential information can be exposed externally.
Original description
The description as published by the source.
ASE/Kalkitech ASE2000 V2 Communication Test Set 2.35 through 2.37 on Windows contains an improper certificate validation vulnerability in the IEC 60870-5-104 TLS client (Task Mode). This allows a network-positioned attacker to bypass certificate validation via a certificate with multiple simultaneous faults, enabling a Man-in-the-Middle attack on protected communications.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-90647 has been found in ASE/Kalkitech ASE2000 V2 Communication Test Set.
Confidential information can be exposed externally. CVSS score: 7.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "ASE/Kalkitech ASE2000 V2 Communication Test Set CVE-2026-90647" on the vendor's site.
CVE-2026-90647 (ASE/Kalkitech ASE2000 V2 Communication Test Set) — CWE-295 / CVSS v3 7.4
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-295) exists in ASE/Kalkitech ASE2000 V2 Communication Test Set.
Check the vendor advisory for the affected versions of ASE/Kalkitech ASE2000 V2 Communication Test Set.
Severity: High (CVSS 7.4/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで ASE/Kalkitech ASE2000 V2 Communication Test Set を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web ase-systems.com
- web nvd.nist.gov
- web github.com