Skip to content

QWED's infrastructure is attested by Docker, Snyk, CircleCI, Netlify, Mintlify, Sentry, Cloudflare, CodeRabbit, NVIDIA Inception, Buildkite, GitLab, Heroku, Atlassian.

Security Advisory · qwedCVE-2026-55585

Authenticated Remote Code Execution via Unsafe SymPy parse_expr()

Status:Fixed
Published:
Package
qwed
Severity & Score
High — CVSS 3.1: 8.8
Affected Versions
5.1.1
Fixed Version
5.1.2
Weakness: CWE-94, Improper Control of Generation of Code (Code Injection)

Summary

CVE-2026-55585 affects qwed 5.1.1. The affected mathematical-expression parsing paths did not sufficiently restrict caller-controlled expressions. In applicable deployments, this could allow arbitrary code execution in the API server process. The issue is fixed in qwed 5.1.2.

Who is affected

You should review and upgrade if you deployed qwed 5.1.1, especially where the affected verification endpoints or batch flows could process tenant-controlled mathematical expressions. If you are already running qwed 5.1.2 or later, confirm that your deployed artifact and dependency lock files reflect the fixed release.

Remediation

Upgrade to qwed 5.1.2 or later. Review the published GitHub Security Advisory and the fixed release for complete version-specific guidance. If the affected version was exposed in a multi-tenant or production deployment, follow your organization’s incident-response process to assess logs, secrets, and downstream exposure.

Primary action: Upgrade to qwed 5.1.2 or later

Technical impact

The issue involved unsafe mathematical-expression parsing in supported API and batch-verification paths. The remediation replaced direct production parsing with a restricted safe-parsing boundary and added validation and regression coverage. The full technical record is available in the GitHub Security Advisory and the remediation pull request.

Disclosure timeline

8 June 2026

Remediation proposed

PR #200 was opened by Sebastian Höpfl / @sebastionoss, providing a public safe-parsing remediation proposal.[Source]

14 June 2026

Remediation merged & advisory published

PR #200 was merged; the GitHub Security Advisory was published.[Source]

14 June 2026

Reporter credit acknowledged

EQSTLab is publicly credited as reporter in the GitHub Security Advisory.[Source]

17 June 2026

CVE identifier assigned

GitHub assigned CVE-2026-55585, according to the advisory’s public history.

Credits

We appreciate the contributors who helped identify, validate, remediate, and disclose this issue. Credit is stated according to the public disclosure record and does not imply a general audit engagement.

RoleContributor
Original public discovery and initial remediation proposalSebastian Höpfl(@Sebastion)Foundation Machines
Independent report and confirmationEQSTLab(@EQSTLab)
Independent analysis2REBCat(@2REBCat)
Verification, hardening, testing, release, and disclosure coordinationQWED-AI maintainers

References

Last reviewed: 14 June 2026