ogham-mcp
Affected
- introduced
0.6.3, fixed0.11.1(ecosystem)
Fixed versions
0.11.1
Fix
- Fixed version
0.11.1pip install --upgrade ogham-mcp==0.11.1
Advisory
Also known as: None
ogham-mcp had credentials embedded in published PyPI sdists -- Neon postgres URLs and Voyage API key
Summary
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 (NEON_US, NEON_EU, NEON_AP vars) | >=0.6.5, <0.11.0 | 21 sdists |
| 1x Voyage AI API key (pa-...) | tests/test_hooks.py::test_mask_secrets_key_value -- test fixture that fed a real key into the redaction-function tester | >=0.6.3, <0.11.1 | 22 sdists |
Impact
make publish-check which scans every sdist for credential patterns before upload.benchmarks/, docs/, research/, extras/, and **/*.env* from all future sdists via explicit hatchling sdist include/exclude in pyproject.toml.Action for users
v0.3.0 through v0.11.0, upgrade to v0.11.1 immediately: pip install --upgrade "ogham-mcp>=0.11.1"
Credit
Discovered during an internal pre-release audit on 2026-04-24 while preparing v0.11.1.
Medium Basis: The source's own band: MODERATE
0.6.3, fixed 0.11.1 (ecosystem)0.11.1
0.11.1pip install --upgrade ogham-mcp==0.11.1Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0