CVE-2026-5556
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA security vulnerability has been detected in badlogic pi-mono up to 0.58.4. This vulnerability affects the function discoverAndLoadExtensions of the file packages/coding-agent/src/core/extensions/loader.ts. The manipulation leads to code injection. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA code injection vulnerability exists in the discoverAndLoadExtensions function within the extension loader (packages/coding-agent/src/core/extensions/loader.ts) of badlogic pi-mono up to version 0.58.4. The function fails to properly sanitize or validate input during the extension discovery and loading process, allowing an attacker to inject malicious code that gets executed in the context of the application.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed version of badlogic pi-monoCheck your package.json or lock file for the pi-mono package version, or run 'npm list pi-mono' or 'yarn list pi-mono' in your project directoryAffected if The version is 0.58.4 or lower
-
Locate the extension loader fileSearch for the file packages/coding-agent/src/core/extensions/loader.ts in your codebase or installed package directoryAffected if The file exists and contains the discoverAndLoadExtensions function
-
Verify extension loading is enabledCheck your project configuration files (such as config files, package.json, or environment variables) for settings that enable or configure the extension loading feature mentioned in loader.tsAffected if Extension loading is enabled or auto-loads on startup
-
Inspect extension loading configurationReview any configuration files or settings that define extension paths, allowed extensions, or extension metadata loading rulesAffected if There are no input validation checks on extension paths or metadata before loading
-
Check for external or untrusted extension sourcesExamine your extension configuration to determine if extensions are loaded from external, untrusted, or user-controlled sources or directoriesAffected if Extensions can be loaded from paths or sources that are not strictly validated or from untrusted locations
You are affected if you are running badlogic pi-mono version 0.58.4 or lower and the extension loading feature in packages/coding-agent/src/core/extensions/loader.ts is enabled with unvalidated extension paths or metadata.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataSince the vendor did not respond to early disclosure, organizations should implement input validation and sanitization on the extension loading mechanism, restrict remote extension sources, and conduct a code review of the discoverAndLoadExtensions function to identify and neutralize injection points.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5556 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-5556 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data