CVE-2026-5631
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 has been found in assafelovic gpt-researcher up to 3.4.3. This affects the function extract_command_data of the file backend/server/server_utils.py of the component ws Endpoint. Such manipulation of the argument args leads to code injection. The attack may be performed from remote. The exploit has been disclosed to the public and may be used. 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 confidenceThe gpt-researcher application up to version 3.4.3 contains a code injection vulnerability in the extract_command_data function within backend/server/server_utils.py, specifically in a WebSocket endpoint. The args parameter is not properly sanitized before use, allowing remote attackers to inject malicious code through the ws endpoint.
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.
-
Check installed gpt-researcher versionRun 'pip show gpt-researcher' or check your package.json/pyproject.toml for the installed version numberAffected if The version number is 3.4.3 or lower
-
Verify WebSocket endpoint is enabledInspect your gpt-researcher configuration or server startup logs to confirm the WebSocket server (backend/server/) is running and accessibleAffected if The WebSocket endpoint is exposed and accepting connections
-
Locate the vulnerable fileFind the file backend/server/server_utils.py in your gpt-researcher installation directory and locate the extract_command_data functionAffected if The file and function exist in the installation
-
Check for unsafe code execution patternInspect the extract_command_data function code: look for eval() or exec() calls that directly use the args parameter without validationAffected if The function contains eval() or exec() applied to args without sanitization or allowlist validation
-
Confirm WebSocket is reachableAttempt a WebSocket connection to the server endpoint (typically ws://localhost:8000 or similar) and verify the extract_command_data function can be invokedAffected if The WebSocket connection succeeds and the function can be called with arbitrary arguments
If gpt-researcher version is 3.4.3 or lower, the WebSocket endpoint is accessible, and backend/server/server_utils.py contains eval/exec on the args parameter without validation, the environment is vulnerable to CVE-2026-5631.
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 and sanitization on the args parameter in extract_command_data, preferably using allowlist validation and avoiding any dynamic code execution functions. Consider using ast.literal_eval or similar safe parsing instead of eval/exec patterns.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5631 — 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-5631 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