CVE-2025-46185
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn Insecure Permission vulnerability in pgcodekeeper 10.12.0 allows a local attacker to obtain sensitive information via the plaintext storage of passwords and usernames.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidencepgcodekeeper 10.12.0 stores usernames and passwords in plaintext without encryption, combined with insecure file permissions that allow local unauthorized users to read these sensitive credential files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed pgcodekeeper versionRun 'pgcodekeeper --version' or check the application's 'About' or version information dialog to determine the exact version numberAffected if Version is 10.12.0 specifically, or any version within the 10.x line prior to remediation
-
Locate credential storage filesSearch the application configuration directory and user data folders for files that may contain username and password entries, such as config files, credential stores, or connection profilesAffected if Credential storage files exist and contain user authentication data
-
Verify credential encryption statusOpen the identified credential files and examine whether the stored passwords appear as plaintext readable strings rather than encrypted, hashed, or otherwise obfuscated valuesAffected if Passwords are stored as readable plaintext without any encryption applied
-
Check file permission settings on credential filesUse 'ls -l' or an equivalent command to view the file permissions on the credential storage files and determine if they allow read access to non-owner users (permissions include 'r' for group or other)Affected if File permissions allow read access by local users other than the file owner (e.g., permissions are 644, 664, or 777 rather than 600 or similar restrictive settings)
-
Assess unauthorized access riskCreate a test using a separate non-privileged local user account to attempt reading the credential filesAffected if A non-owner user can successfully read the credential files due to overly permissive access rights
A user is affected if pgcodekeeper version 10.12.0 is in use and credential files containing plaintext passwords have permissions that allow local unauthorized users to read them.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement encrypted credential storage using a secure vault or encryption mechanism, and ensure proper file permissions restrict access to credential storage locations to authorized users only.
- Consultation3.0 h
- Implementation8.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46185 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-46185 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data