Hard-Coded Cryptographic Key in PIMBoards Exposes Sensitive Data in Project Files
AI analysis
CVE-2026-81821 is a cryptographic weakness in PIMBoards (CWE-321, use of a hard-coded cryptographic key) that leaves data stored in its project files protected only by encryption that anyone can defeat. It is triggered when an attacker with read access to PIMBoards project files — local access per the CVSS 4.0 vector (AV:L with low privileges, no user interaction required) — obtains those files and decrypts them using the embedded key. The attacker gains the ability to decrypt and read sensitive information in the files; the CVSS 4.0 score rates the direct confidentiality impact as High with no direct integrity or availability impact, though subsequent-system confidentiality and integrity impacts are rated High. Users who store PIMBoards project files in locations readable by other users, accounts, or systems are affected, and the source data does not name a vendor or specify affected versions. There are no known public proof-of-concept exploits, no CISA KEV listing, and a low EPSS probability of 0.1%, so exploitation is not currently known to be occurring.
What to do: Restrict read access to PIMBoards project files (file-share ACLs and local permissions), since an attacker only needs read access to decrypt their contents, and assume any secrets or sensitive data stored in those files is readable by anyone who can access them. Because no fixed version or patch level is specified in the available data, monitor the vendor and CISA ICS advisories for a remediation release, and remove or rotate any credentials or sensitive material stored in PIMBoards project files once a fix is available.
Estimated exposure
—No basis for an estimate.
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Description
The vulnerability, if exploited, could allow a miscreant with read access to PIMBoards project files to decrypt and view sensitive information.