ogham-mcp had credentials embedded in published PyPI sdists -- Neon postgres URLs and Voyage API key
GHSA-8pqq-224h-x875 · published 2026-05-05
- Severity
- Medium
- CVSS score
- Not scored
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 0.11.1
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 reviewed post-rotation. Remediation on our side: Neon passwords for all three regions rotated. Voyage API key rotated. All affected versions yanked from PyPI (v0.3.0 through v0.10.4 yanked on 2026-04-24; v0.11.0 pending yank after this advisory). v0.11.0 removed the Neon URLs and introduced make publish-check which scans every sdist for credential patterns before upload.
Upgrade ogham-mcp to 0.11.1 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| ogham-mcp | PyPI | >= 0.6.3, < 0.11.1 | 0.11.1 |
- CriticalPhoenix: Format String Injection in applyChatTemplatearize-phoenix
- CriticalFlowise: Unauthenticated OAuth2 token refresh endpoint returns access tokens — enables token theft for any connected serviceflowise
- CriticalMLflow: Environment variable injection in AI Gateway secrets enables server-side credential exfiltrationmlflow
- CriticalvLLM has RCE In Video Processingvllm
- HighConfig revision hashes could expose password verifiersopenclaw
- Highn8n: Shared Credential Header Leak via HTTP Request Pagination Expressionn8n, n8n, n8n
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.