CVE-2026-113455: KSeF API Secret Exposure in VisualNet visualTicket
VisualNet visualTicket versions before 20260817 expose the KSeF API integration secret in the administrative settings panel. The KSeF - Token API edit form renders the actual stored secret in a pre-filled, unmasked field, allowing anyone able to view the form to read the integration credential.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Disclosure of the KSeF API integration secret compromises credential confidentiality and may enable unauthorized use of the KSeF integration within the token's assigned permissions.
Mitigation
If you can’t patch tonight, do this now.
Restrict access to the administrative settings panel to trusted personnel and avoid displaying the affected form during screen sharing or recording. If exposure is suspected, revoke and replace the KSeF API integration token.
Remediation
Patch, then assume compromise.
Upgrade VisualNet visualTicket to version 20260817 or later, which fixes the vulnerability.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Frequently asked questions
- Is CVE-2026-113455 exploited in the wild?
- As of Nov 17, 2026, Mallory has no reports of CVE-2026-113455 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-113455?
- As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-113455.
- Is there a patch for CVE-2026-113455?
- Upgrade VisualNet visualTicket to version 20260817 or later, which fixes the vulnerability.
- How severe is CVE-2026-113455?
- CVE-2026-113455 has a CVSS v4 score of 5.1 (Medium) and an EPSS score of 0.32% (25th percentile) as of Nov 17, 2026.
Recent activity
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.