CVE-2025-46185 Information disclosure in n/a
Medium 6.2
Published
Updated
Check this codebase for CVE-2025-46185 and fix it if it is affected.
What it is: CVE-2025-46185 is a medium-severity vulnerability in n/a, published on 24 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-46185 in the wild and no public exploit code.
Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2025-46185/ (Markdown: https://insights.sbomify.com/CVE-2025-46185/index.md)
A local attacker can obtain sensitive credentials due to insecure plaintext storage of passwords and usernames in pgcodekeeper.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-46185?
CVE-2025-46185 is a medium-severity vulnerability in n/a, published on 24 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
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.
Weakness: CWE-276
Which versions are affected by CVE-2025-46185?
How do I fix CVE-2025-46185?
No fix has been published for CVE-2025-46185 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-46185 being exploited?
There is no known exploitation of CVE-2025-46185 in the wild and no public exploit code.
Sources
Also known as GHSA-xpp7-3x3w-4w29.