GHSA-8pqq-224h-x875: Ogham mcp Ogham-mcp Had Credentials Embedded Vulnerability
MODERATEGHSA-8pqq-224h-x875 is a MODERATE ogham-mcp had credentials embedded vulnerability (CWE-798: Use of Hard-coded Credentials) affecting Ogham mcp libraries in the PyPI ecosystem. The issue involves ogham-mcp had credentials embedded in published pypi sdists -- neon postgres urls and voyage api key. Remediation is available by upgrading affected packages to version 0.11.1.
GHSA-8pqq-224h-x875 at a Glance
How to Fix GHSA-8pqq-224h-x875
To remediate this vulnerability, upgrade all affected Ogham mcp dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
pip install ogham-mcp>=0.11.1Run the following command in your project directory to verify that all resolved dependencies use the patched release:
pip show ogham-mcpHow to Check if You Are Affected
To determine whether your Python environment is affected by GHSA-8pqq-224h-x875, inspect your installed packages using pip:
pip show ogham-mcpAnalyze the terminal output to locate any version of Ogham mcp in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.11.1), your application is affected.
Note: The pip show ogham-mcp command checks currently installed packages in your active Python environment.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-798: Use of Hard-coded Credentials, where the product contains hard-coded credentials, such as a password or cryptographic key. In Ogham mcp, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
GHSA-8pqq-224h-x875 Affected Ogham mcp Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
ogham-mcp
|
PyPI |
≥ 0.6.3
< 0.11.1
|
0.11.1
|
References
Frequently Asked Questions
What is GHSA-8pqq-224h-x875?
Which Ogham mcp versions are affected?
What version fixes GHSA-8pqq-224h-x875?
Is ogham-mcp affected?
What CWE is associated with GHSA-8pqq-224h-x875?
How can I check PyPI dependencies for GHSA-8pqq-224h-x875?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-8pqq-224h-x875",
"modified" : "2026-05-05T00:03:49Z",
"published" : "2026-05-05T00:03:48Z",
"aliases" : [ ],
"summary" : "ogham-mcp had credentials embedded in published PyPI sdists -- Neon postgres URLs and Voyage API key",
"details" : "## Summary\n\nBetween 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.\n\n## What was leaked\n\n| Credential | Location in sdist | Vulnerable range | Count |\n|---|---|---|---|\n| 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 |\n| 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 |\n\n## Impact\n\n- **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.\n- **Observed exploitation**: none detected. Audit logs on both providers were reviewed post-rotation.\n- **Remediation on our side**:\n - Neon passwords for all three regions rotated.\n - Voyage API key rotated.\n - 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).\n - v0.11.0 removed the Neon URLs and introduced `make publish-check` which scans every sdist for credential patterns before upload.\n - 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 in `pyproject.toml`.\n\n## Action for users\n\n- If users installed any version from `v0.3.0` through `v0.11.0`, upgrade to **v0.11.1** immediately:\n ```\n pip install --upgrade \"ogham-mcp>=0.11.1\"\n ```\n- Users do not need to rotate anything on their end. The leaked credentials were owned by the project maintainer, not by users.\n\n## Credit\n\nDiscovered during an internal pre-release audit on 2026-04-24 while preparing v0.11.1.",
"severity" : [ ],
"affected" : [ {
"package" : {
"ecosystem" : "PyPI",
"name" : "ogham-mcp"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0.6.3"
}, {
"fixed" : "0.11.1"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/ogham-mcp/ogham-mcp/security/advisories/GHSA-8pqq-224h-x875"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/ogham-mcp/ogham-mcp"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-798" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-05-05T00:03:48Z",
"nvd_published_at" : null
}
}