What is CVE-2026-19583?

CVE-2026-19583 is Velociraptor Required Permissions bypass by using client monitoring queries. The supplied enrichment data classifies it as Access Control mapped to CWE-732 CWE-732.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-19583. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-19583 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

3 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-19583 using CVSS 9.9, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

criticalAccess Controlpublic exploit

CVE-2026-19583

CVE-2026-19583 — Velociraptor Required Permissions bypass by using client monitoring queries

Velociraptor allows some sensitive artifacts to be gated by additional permissions. For example, the Linux.Sys.BashShell artifact allows arbitrary command execution on endpoints, and so it requires the EXECVE permission to schedule. However, no such check was implemented for client monitoring artifacts. Additionally there was no requirement that client monitoring artifacts carry the CLIENT_EVENTS type. This allows any user who can schedule client monitoring artifacts to also schedule otherwise restricted artifacts (such as Linux.Sys.BashShell).

Published Sep 10, 2026Updated Sep 10, 2026Sources: NVD, Rapid7 (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

ahead of 0% of scored CVEs

Affects

Rapid7

Velociraptor

CVSS base

9.9

critical

Remediation

The vendor's own words where we have them.

Upgrade Velociraptor to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Rapid7	Velociraptor	0 to < 0.77.2	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

Low

Confidentiality

High

Integrity

High

Scope

Changed

Attack Complexity

Low

Attack Vector

Network

Privileges Req

Low

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
9.9	CVSS 3.1	critical	3.1	6	rapid7.com (CNA), Rapid7 (CNA), GHSA

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-732 · Incorrect Permission Assignment for Critical Resource

Read Application Data
Read Files or Directories
Gain Privileges or Assume Identity
Modify Application Data

Mitigation: When using a critical resource such as a configuration file, check to see if the resource has insecure permissions (such as being modifiable by any regular user) [REF-62], and generate an error or even exit the software if there is a possibility that the resource could have been modified by an unauthorized party.

Weakness & attack patterns

CWE-732

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-1 · Accessing Functionality Not Properly Constrained by ACLsCAPEC-206 · Signing Malicious CodeCAPEC-234 · Hijacking a privileged processCAPEC-122 · Privilege AbuseCAPEC-127 · Directory IndexingCAPEC-17 · Using Malicious FilesCAPEC-180 · Exploiting Incorrectly Configured Access Control Security LevelsCAPEC-60 · Reusing Session IDs (aka Session Replay)CAPEC-61 · Session FixationCAPEC-62 · Cross Site Request ForgeryCAPEC-642 · Replace Binaries

T1574.010Hijack Execution Flow: ServicesFile Permissions Weakness
T1548Abuse Elevation Control Mechanism
T1083File and Directory Discovery

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable Velociraptor.
Monitor for scanner or exploit-pattern traffic after 3 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 9.9 (AV:N)
Sep 10, 2026 · NVD
Initial · CVE published
Sep 10, 2026 · NVD
Added · GHSA-jfjq-fc5j-227m published (critical)
Sep 10, 2026 · GitHub Security Advisory
CVE published by MITRE.
Sep 10, 2026 · SOCRadar CTI

References

4 on the record

docs.velociraptor.app/announcements/advisories/cve-2026-19583/
Vendor Advisory, Mitre
github.com/Velocidex/velociraptor/pull/4967
Exploit, Third Party Advisory, Mitre
nvd.nist.gov/vuln/detail/CVE-2026-19583
NVD
github.com/advisories/GHSA-jfjq-fc5j-227m
Exploit, Third Party Advisory

Elsewhere on this site

Rapid7every CVE for this vendor
Access Controlsame class
CWE-732other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-19583 is Velociraptor Required Permissions bypass by using client monitoring queries, a critical vulnerability affecting Velociraptor from Rapid7. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-19583. Public exploit evidence is: 3 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 9.9 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.