CVE-2025-8697
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 vulnerability was found in agentUniverse up to 0.0.18 and classified as critical. This issue affects the function StdioServerParameters of the component MCPSessionManager/MCPTool/MCPToolkit. The manipulation leads to os command injection. The attack may be initiated remotely. The exploit has been disclosed to the public 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 command injection vulnerability exists in the StdioServerParameters function within the MCPSessionManager/MCPTool/MCPToolkit component of agentUniverse up to version 0.0.18. The function fails to properly sanitize input before passing it to OS-level command execution, allowing an attacker to inject arbitrary shell commands. The vulnerability is remotely exploitable and public exploits are available.
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 if agentUniverse is installedLocate the agentUniverse package in your environment using package managers (pip list, npm list, or similar), or search for agentUniverse directories in your project.Affected if agentUniverse is present in your environment
-
Check the installed version of agentUniverseRun a version check command for agentUniverse (e.g., pip show agent universe, npm list agent-universe, or inspect the package version in your lock file).Affected if The installed version is 0.0.18 or any version prior to 0.0.18
-
Verify if MCPToolkit or MCPTool component is in useSearch your codebase for imports or references to MCPToolkit, MCPTool, or MCPSessionManager modules from agentUniverse.Affected if Your code imports or uses MCPToolkit, MCPTool, or MCPSessionManager components
-
Check if StdioServerParameters function is invokedSearch your codebase for any calls to StdioServerParameters function, particularly where external input may be passed as arguments.Affected if Your code calls StdioServerParameters function, especially with user-supplied or network-supplied input
-
Inspect configuration for StdioServerParameters usageReview your application configuration files, environment variables, or runtime settings that may configure or invoke the StdioServerParameters function.Affected if StdioServerParameters is configured or enabled in your deployment
You are affected if agentUniverse version 0.0.18 or lower is installed and your environment uses the MCPToolkit/MCPTool component with the StdioServerParameters function exposed to external input.
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 dataUpgrade agentUniverse to a version beyond 0.0.18 that patches the command injection in StdioServerParameters. If no patched version is available, implement strict input validation and use parameterized command execution methods instead of shell string interpolation.
- 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-2025-8697 — 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-2025-8697 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