Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
Low

Cleartext Transmission of Sensitive Information in STER

IdentifiersCVE-2026-25608CWE-319· Cleartext Transmission of…

CVE-2026-25608 affects STER software from Centralny Instytut Ochrony Pracy - Państwowy Instytut Badawczy in versions prior to 9.5. The vulnerability arises because STER transmits data over unencrypted TCP traffic, resulting in sensitive information being sent in cleartext across the network. Because the application does not adequately protect data in transit, an attacker who can observe or intercept the network path can perform a man-in-the-middle attack and capture transmitted secrets. Exposed data may include passwords, personal data, and authentication tokens.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can lead to disclosure of sensitive information transmitted between STER components or clients and servers. An attacker positioned on the network path can intercept credentials, personal data, and session or authentication tokens, which may in turn enable unauthorized account access, session hijacking, privacy violations, and further compromise of affected environments depending on what intercepted data is reused elsewhere.

Mitigation

If you can’t patch tonight, do this now.

Until the fixed version can be deployed, reduce exposure by ensuring STER traffic is not sent over untrusted or shared networks, placing the application behind encrypted transport such as a VPN or other secure tunnel where feasible, and restricting network access to trusted segments to reduce opportunities for man-in-the-middle interception. The provided content does not specify any vendor-endorsed workaround beyond upgrading to version 9.5.

Remediation

Patch, then assume compromise.

Upgrade STER to version 9.5 or later. The issue was fixed in version 9.5.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
SterSterapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity1

Community discussion across Reddit, Mastodon, and other social sources.