CVE-2026-7398
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 weakness has been identified in florensiawidjaja BioinfoMCP up to 7ada7918b9e515604d3c0ae264d3a9af10bf6e54. This vulnerability affects the function Upload of the file bioinfo_mcp_platform/app.py of the component Upload Endpoint. This manipulation of the argument Name causes path traversal. The attack can be initiated remotely. The exploit has been made available to the public and could be used for attacks. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. The project was informed of the problem early through an issue report but has not responded yet.
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 confidencePath traversal vulnerability in the file upload endpoint of BioinfoMCP. The 'Name' parameter in the Upload function of bioinfo_mcp_platform/app.py is not properly validated, allowing attackers to manipulate file paths using '..' sequences to write files outside the intended upload directory.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/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 BioinfoMCP versionLocate the bioinfo_mcp_platform installation and check for version information in package metadata, setup files, or version constants. Compare your installed version to the affected range.Affected if Your version is within an affected range or is an unpatched version of BioinfoMCP.
-
Locate the Upload function in app.pyFind the file bioinfo_mcp_platform/app.py and locate the Upload function definition. Confirm it accepts a 'Name' parameter.Affected if The Upload function with a 'Name' parameter exists in your installation.
-
Determine if the upload endpoint is exposedCheck the application's routing or URL configuration to see if the Upload function is exposed as an accessible HTTP endpoint.Affected if The file upload endpoint is reachable over the network.
-
Inspect Name parameter validationExamine the Upload function code to determine whether the 'Name' parameter is validated. Specifically look for code that filters or rejects path traversal sequences like '..'.Affected if No validation logic blocks '..' or similar path traversal sequences in the 'Name' parameter.
-
Verify upload directory restrictionsCheck the application configuration and upload handling code to see if uploaded files are restricted to a specific directory with proper access controls.Affected if Files can be written outside the intended upload directory due to missing restrictions.
You are affected if BioinfoMCP is running with the Upload function exposed and the 'Name' parameter lacks validation to block path traversal sequences, allowing files to be written outside the intended directory.
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 dataImplement strict input validation on the 'Name' parameter to reject path traversal sequences ('..') and restrict filenames to only allow safe characters. Additionally, enforce that uploaded files are stored within a designated secure directory with proper access controls.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7398 — 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-7398 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