pgcodekeeper 10.12.0 permission

Summaryinfo

A vulnerability was found in pgcodekeeper 10.12.0. It has been classified as problematic. This impacts an unknown function. The manipulation leads to permission. This vulnerability is traded as CVE-2025-46185. An attack has to be approached locally. There is no exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in pgcodekeeper 10.12.0. This issue affects an unknown code block. The manipulation with an unknown input leads to a permission vulnerability. Using CWE to declare the problem leads to CWE-275. Impacted is confidentiality. The summary by CVE is:

An Insecure Permission vulnerability in pgcodekeeper 10.12.0 allows a local attacker to obtain sensitive information via the plaintext storage of passwords and usernames.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2025-46185 since 04/22/2025. The exploitation is known to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1222 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-35855). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• pgcodekeeper

Version

• 10.12.0

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion