CVE-2026-0809: Streamsoft Prestiż · Weak Encoding for Password
Affects Streamsoft PrestiżSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 20.0.380.92 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 20.0.380.92
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 12 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade Streamsoft Prestiż to 20.0.380.92.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| StreamsoftStreamsoft Prestiż | Affected
| Fixed in
|
AI-suggested
- Immediate upgrade to Streamsoft Prestiż version 20.0.380.92 or later, where the vulnerability has been fixed, is the most effective mitigation.
- Implement network segmentation and restrict access to the Streamsoft Prestiż application servers to trusted internal networks only, reducing exposure to remote attackers.
- Monitor and audit token usage logs for unusual patterns or repeated failed attempts to guess tokens, which may indicate exploitation attempts.
- Employ additional application-layer encryption or tokenization mechanisms if possible, to add layers of security beyond the built-in encoding.
- Conduct regular security assessments and penetration testing focused on authentication and token management components.
- Educate staff and users about the importance of timely patching and secure handling of sensitive tokens.
- Coordinate with Streamsoft support and national cybersecurity authorities for updates and guidance on secure deployment practices.
- Consider implementing anomaly detection systems that can flag suspicious activities related to token usage or e-invoicing transactions. These steps go beyond generic advice by focusing on network controls, monitoring, and layered security to mitigate risks while patching is underway or in case of delayed upgrades.
Description
Use of a custom token encoding algorithm in Streamsoft Prestiż software allows the value of the KSeF (Krajowy System e-Faktur) token to be guessed after analyzing how tokens with know values are encoded. This issue was fixed in version 20.0.380.92.