Read the docs
TI-2026-20707 Aliases CVE-2026-25600GHSA-9pjg-jh77-2mjg

Credential Exposure Vulnerability in Trac PDBM

Priority LOW 29CWE-798Published · Updated

Key facts

Attack vector
Local
Privileges required
High
User interaction
None
Attack complexity
High
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · High
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-798.

Summary

The PDBM application relies on a static, hard‑coded secret embedded in the PDBM.exe executable. This secret is used by the application’s encryption routines, including the function responsible for decrypting credentials stored in the product’s configuration file. Because the secret is constant across installations, any attacker with sufficient local privileges can extract it from the binary. Once obtained, the secret allows the attacker to decrypt the stored password and authenticate as the user defined in the configuration file. In the affected version, this user account is configured with administrative privileges, granting full access to PDBM’s management interface and its underlying operational functions.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00065 0th percentileScored 2026-11-07
Fix Fixed PDBM (Trac d.o.o.): 2.0.0.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
Trac d.o.o.PDBMbefore 2.0.0.02.0.0.0Patch availableCNA
  • PDBM VendorTrac d.o.o. Affected before 2.0.0.0 Fixed in 2.0.0.0 Patch available CNA

Remediation

  • Fix · CNA PDBM (Trac d.o.o.) Fixed in 2.0.0.0

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-25600
  2. 2026-10-03 Alias added: GHSA-9pjg-jh77-2mjg

References

Sources