What is GHSA-8PQQ-224H-X875?

GHSA-8PQQ-224H-X875 is a medium-severity use of hard-coded credentials vulnerability in ogham-mcp (pip), affecting versions >= 0.6.3, < 0.11.1. It is fixed in 0.11.1. Credentials are embedded in source code or a binary, making them accessible to anyone who can read the artifact.

Which versions of ogham-mcp are affected by GHSA-8PQQ-224H-X875?

ogham-mcp (pip) versions >= 0.6.3, < 0.11.1 is affected.

Is there a fix for GHSA-8PQQ-224H-X875?

Yes. GHSA-8PQQ-224H-X875 is fixed in 0.11.1. Upgrade to this version or later.

Is GHSA-8PQQ-224H-X875 exploitable, and should I be worried?

Whether GHSA-8PQQ-224H-X875 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-8PQQ-224H-X875 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-8PQQ-224H-X875 in ogham-mcp

Q: Which versions of ogham-mcp are affected by GHSA-8PQQ-224H-X875?

ogham-mcp (pip) versions >= 0.6.3, < 0.11.1 is affected.

Q: Is there a fix for GHSA-8PQQ-224H-X875?

Yes. GHSA-8PQQ-224H-X875 is fixed in 0.11.1. Upgrade to this version or later.

Q: Is GHSA-8PQQ-224H-X875 exploitable, and should I be worried?

Whether GHSA-8PQQ-224H-X875 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-8PQQ-224H-X875 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-8PQQ-224H-X875?

Upgrade ogham-mcp to 0.11.1 or later.

Summary

ogham-mcp had credentials embedded in published PyPI sdists -- Neon postgres URLs and Voyage API key

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

Action for users

If users installed any version from v0.3.0 through v0.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.

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-check which 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 in pyproject.toml.

Credentials are embedded in source code or a binary, making them accessible to anyone who can read the artifact. Typical impact: unauthorized access using the static credential.

Affected versions

ogham-mcp (>= 0.6.3, < 0.11.1)

Security releases

ogham-mcp → 0.11.1 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade ogham-mcp to 0.11.1 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-8PQQ-224H-X875? GHSA-8PQQ-224H-X875 is a medium-severity use of hard-coded credentials vulnerability in ogham-mcp (pip), affecting versions >= 0.6.3, < 0.11.1. It is fixed in 0.11.1. Credentials are embedded in source code or a binary, making them accessible to anyone who can read the artifact.
Which versions of ogham-mcp are affected by GHSA-8PQQ-224H-X875? ogham-mcp (pip) versions >= 0.6.3, < 0.11.1 is affected.
Is there a fix for GHSA-8PQQ-224H-X875? Yes. GHSA-8PQQ-224H-X875 is fixed in 0.11.1. Upgrade to this version or later.
Is GHSA-8PQQ-224H-X875 exploitable, and should I be worried? Whether GHSA-8PQQ-224H-X875 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-8PQQ-224H-X875 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-8PQQ-224H-X875? Upgrade ogham-mcp to 0.11.1 or later.