{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-25600 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-25600 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-25600 is a medium-severity vulnerability in Trac d.o.o. PDBM, published on 1 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-25600 and fix it if it is affected.\n\nWhat it is: CVE-2026-25600 is a medium-severity vulnerability in Trac d.o.o. PDBM, published on 1 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-25600 in the wild and no public exploit code.\n\nAffected product: Trac d.o.o. PDBM. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-25600/ (Markdown: https://insights.sbomify.com/CVE-2026-25600/index.md)","id":"CVE-2026-25600","markdown":"https://insights.sbomify.com/CVE-2026-25600/index.md","name":"CVE-2026-25600","record":{"aliases":["GHSA-9pjg-jh77-2mjg"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["privilege_escalation","account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"PDBM application","requires_auth":"high_privilege","summary":"Attackers with local access can extract a hardcoded secret to decrypt credentials and gain administrative privileges in the PDBM application.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ENISA","cpe":[],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"The PDBM application relies on a static, hard‑coded secret embedded \nin the PDBM.exe executable. This secret is used by the application’s \nencryption routines, including the function responsible for decrypting \ncredentials stored in the product’s configuration file. Because the \nsecret is constant across installations, any attacker with sufficient \nlocal privileges can extract it from the binary. Once obtained, the secret allows the attacker to decrypt the stored \npassword and authenticate as the user defined in the configuration file.\n In the affected version, this user account is configured with \nadministrative privileges, granting full access to PDBM’s management \ninterface and its underlying operational functions.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Credential Exposure Vulnerability in Trac PDBM","id":"CVE-2026-25600","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Credential Exposure vulnerability in MEPIS RM","id":"CVE-2026-25601"},"packages":[],"prev":{"headline":"Missing authentication and clear‑text data transmission affecting Orca heat pumps","id":"CVE-2026-25599"},"products":["PDBM"],"published":"2026-06-01","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-01","vendors":["Trac d.o.o."]},"summary":"Attackers with local access can extract a hardcoded secret to decrypt credentials and gain administrative privileges in the PDBM application.","url":"https://insights.sbomify.com/CVE-2026-25600/"}