UnratedPyPIAmendedPublished
ogham-mcp had credentials embedded in published PyPI sdists -- Neon postgres URLs and Voyage API key
GHSA-8pqq-224h-x875
- Affected
- PyPI ogham-mcp >= 0.6.3, < 0.11.1
- Fixed in
- 0.11.1· Vendor fix available
- Issue
- Between 2026-02 and 2026-04-24 a total of 22 public PyPI sdists of ogham-mcp contained development credentials embedded in source files. All credentials have since been rotated on the respective providers. No known exploitation. Upgrade to v0.11.1 to get a clean release. What was leaked | Credential | Location in sdist | Vulnerable range | Count | |---|---|---|---| | 3x Neon postgres URLs with passwords (US / EU / AP development databases) | top-level Makefile (NEONUS, NEONEU, NEONAP vars) | =0.6.5, <0.11.0 | 21 sdists | | 1x Voyage AI API key (pa-...) | tests/testhooks.py::testmasksecretskeyvalue -- test fixture that fed a real key into the redaction-function tester | =0.6.3, <0.11.1 | 22 sdists | Impact - Primary risk: any consumer of the affected sdists could have extracted the credentials and used them. The Neon URLs pointed at development databases; the Voyage key was a rate-limited API key. - Observed exploitation: none detected. Audit logs on both providers were…
Recommended action: Upgrade to 0.11.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.