GHSA-8pqq-224h-x875: ogham-mcp had credentials embedded in published PyPI sdists -- Neon postgres URLs and Voyage API key
Twenty-two PyPI source distributions of the ogham-mcp MCP server, published between February and 24 April 2026, contained the maintainer's development credentials: three Neon Postgres URLs with passwords and one Voyage AI API key. All were rotated, and no exploitation was detected. Upgrade to ogham-mcp 0.11.1 for a clean release. Users have nothing to rotate.
Published May 5, 2026 · Analysis Oct 28, 2026
What an attacker can do
This is a packaging leak, not a code flaw. The credentials belonged to the project maintainer, not to users.
The Neon URLs sat in the top-level Makefile of 21 sdists, as the NEON_US, NEON_EU and NEON_AP variables, and pointed at development databases in three regions. They affect versions from 0.6.5 up to but not including 0.11.0. The Voyage key (prefix pa-) sat in tests/test_hooks.py, in the test_mask_secrets_key_value fixture that fed a real key to the redaction-function test. It affects 22 sdists, from 0.6.3 up to but not including 0.11.1. The Voyage key was rate-limited.
Anyone who downloaded one of those sdists could read the secrets and use them against the maintainer's accounts. The maintainer reports they reviewed audit logs on both providers after rotation and found no exploitation. For a user, the direct risk is small: no user data or credentials are involved. The lesson for teams is about supply chain hygiene, since the same mistake in your own package would expose your keys.
Who is affected
The pip package ogham-mcp. The advisory metadata gives >= 0.6.3 and < 0.11.1, while the maintainer's action text and yank list begin at v0.3.0 and run through v0.11.0. The page does not explain that gap, so treat any version below 0.11.1 as affected. Check yours:
pip show ogham-mcpogham-mcp
- Ecosystem
- PyPI
- Affected
- >= 0.6.3, < 0.11.1
- Fixed in
- 0.11.1
- Check
pip show ogham-mcp
How to fix it
Upgrade to ogham-mcp 0.11.1:
pip install --upgrade "ogham-mcp>=0.11.1"Version 0.11.0 removed the Neon URLs and added a make publish-check step that scans every sdist for credential patterns before upload. Version 0.11.1 removes the Voyage key from the test fixture and excludes benchmarks/, docs/, research/, extras/ and any **/*.env* files from future sdists. The maintainer yanked v0.3.0 through v0.10.4 on 2026-04-24 and listed v0.11.0 as pending yank. You do not need to rotate anything yourself.
How to tell if you were hit
Run pip show ogham-mcp or check your lock file and requirements for versions below 0.11.1. Mirrors, internal caches and CI images may still hold old sdists, so search them too. If you mirror or scan packages, grep the Makefile and tests/test_hooks.py of old sdists for Neon connection strings and a pa- key. The maintainer reports no unauthorized use in provider audit logs.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
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
- 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-checkwhich scans every sdist for credential patterns before upload. - v0.11.1 scrubs the Voyage key from the test fixture and excludes
benchmarks/,docs/,research/,extras/, and**/*.env*from all future sdists via explicit hatchling sdist include/exclude inpyproject.toml.
Action for users
- If users installed any version from
v0.3.0throughv0.11.0, upgrade to v0.11.1 immediately: ``pip install --upgrade "ogham-mcp>=0.11.1"`` - Users do not need to rotate anything on their end. The leaked credentials were owned by the project maintainer, not by users.
Credit
Discovered during an internal pre-release audit on 2026-04-24 while preparing v0.11.1.
Questions
- Do I need to rotate any credentials after installing an affected ogham-mcp?
No. The advisory says the leaked credentials belonged to the project maintainer, not users. Upgrading to 0.11.1 is the only step.
- Were the leaked credentials used by attackers?
The maintainer reports no exploitation. They reviewed audit logs on both providers after rotating the Neon passwords and the Voyage key.
- Does this advisory have a CVE?
No. It is tracked as GHSA-8pqq-224h-x875 only, with CWE-798 for hard-coded credentials.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More Other MCP servers and tools vulnerabilities
All Other MCP servers and tools entriesCVE-2026-102943
Dagu MCP DAG specification read bypasses path containment and workspace isolation
medium6.5Nov 10, 2026CVE-2026-102610
fast-agent: `fast-agent serve` binds HTTP to 0.0.0.0 with no authentication by default; with --shell this is unauthenticated remote command execution
medium6.4Nov 9, 2026CVE-2026-63655
tsParticles: Unbounded HTTP Request Body Buffering in @tsparticles/mcp-server Leads to Remote DoS
high7.5Nov 9, 2026CVE-2026-76892
tsParticles: Malformed JSON requests can terminate the @tsparticles/mcp-server HTTP process
high8.7Nov 9, 2026CVE-2026-76893
tsParticles: A single anonymous MCP session can monopolize HTTP mode and deny new clients
medium6.9Nov 9, 2026CVE-2026-77604
Code Graph RAG: MCP paginated read_file path traversal / arbitrary file read
high7.5Nov 9, 2026
