VulnerabilityPublished 22 Oct 2026

CVE-2026-51954: webasyst-framework

Affects webasyst-frameworkSource CVE Database V5

Not known to be exploited : upgrade to 4.0.4 soon.

Data as of 26 Oct 2026, 17:30 UTC

Severity

High

Rated High by the CNA (mitre) · No CVSS score from NVD or the CNA

EPSS: 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.0.4

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade webasyst/webasyst-framework to 4.0.4.

Affected software

Product	Affected	Fixed in
GitHubwebasyst/webasyst-framework`pkg:github/webasyst/webasyst-framework`Other threats	Affected <4.0.4	Fixed in 4.0.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Webasyst Framework version 4.0.4. Users should upgrade to version 4.0.4 or later to remediate this vulnerability. No vendor advisory content was provided, so check the official Webasyst resources for confirmation and additional guidance.

Description

A vulnerability in Webasyst Framework versions 4.0.3 and earlier allows remote attackers to execute arbitrary code by crafting a malicious OAuth authorization URL with an arbitrary redirect_uri parameter.

References

Community reviews

Loading reviews…