CVE-2026-120387
validatedZero produced an exploit or a check.GHSA-qf25-prv2-v3mp ↗EUVD-2026-126913 ↗
description
PowerStudio SCADA Wave releases before 24.11.17.0 have a JWT validation weakness. An unauthenticated remote attacker who can reach the affected service may bypass authentication and operate with another user's permissions.
mitigation
Upgrade PowerStudio SCADA Wave to version 24.11.17.0 or later. Restrict network access to the affected service until the update is deployed.
fixed in 24.11.17.0
outcome
Contextual check: a technique exists and was validated, but no deterministic check could cover this one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-11-17 04:47Zcve_org: trigger signal, started the run
- 2026-11-17 05:59ZExploit-Garbage/0day-Rubbish
this entry in the feed
GET /api/v1/feed/CVE-2026-120387
{ "etk_id": "ETK-2026-4647", "cve_id": "CVE-2026-120387", "display_id": "CVE-2026-120387", "ghsa_id": "GHSA-qf25-prv2-v3mp", "euvd_id": "EUVD-2026-126913", "status": "published", "anchor_state": "anchored", "title": "JWT signature verification flaw in PowerStudio SCADA Wave", "summary": "PowerStudio SCADA Wave releases before 24.11.17.0 have a JWT validation weakness. An unauthenticated remote attacker who can reach the affected service may bypass authentication and operate with another user's permissions.", "mitigation": "Upgrade PowerStudio SCADA Wave to version 24.11.17.0 or later. Restrict network access to the affected service until the update is deployed.", "vendor": "Circutor", "product": "PowerStudio SCADA Wave", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 24.8.0, < 24.11.17.0" ], "ecosystem": null, "fixed_versions": [ "24.11.17.0" ], "package_name": "PowerStudio SCADA Wave", "purl": null } ], "cwes": [ 347 ], "cvss_score": 10, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H", "epss_score": 0.0035, "epss_percentile": 0.2909, "epss_asof": "2026-11-17", "automation": "contextual", "check": true, "check_confidence_basis": "assessed", "exploit": false, "pipeline_minutes": 35.60950868333333, "t0_at": "2026-11-17T04:47:30.045000+00:00", "signals": { "check": { "at": "2026-11-18T08:01:36.201968+00:00", "days": 1.134793483425926, "is_lower_bound": false, "measured_at": "2026-11-17T04:47:30.045000+00:00", "url": null }, "public_poc": { "at": "2026-07-24T09:18:37+00:00", "days": -115.81172505787038, "is_lower_bound": false, "measured_at": "2026-11-17T04:47:30.045000+00:00", "url": "https://github.com/Exploit-Garbage/0day-Rubbish" }, "trigger_signal": { "at": "2026-11-17T04:47:30.045000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-11-17T04:47:30.045000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-120387" } } }
published 2026-11-17 05:50Z
last change 2026-11-18 21:29Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.