Skip to main content
VulnerabilityPublished

CVE-2026-18819: RackTables · Cross-Site Request Forgery

Affects RackTablesSource CVE Database V5

0
Compare

Public exploit available · CVSS 5.3 Medium.

Data as of 1 Nov 2026, 22:58 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
RackTablesAffected
  • 0.1 – 0.22.0
22 affected builds
Fixed in–
GitHubfa1c4/racktablespkg:github/fa1c4/racktablesOther threatsAffected
  • 0.1 – 0.22.0
22 affected builds
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:racktables:racktables:*:*:*:*:*:*:*:*

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

AI-suggested

Since the project maintainer has not provided an official fix or mitigation, users should consider implementing custom CSRF protections or other compensating controls until an official patch is released.

Description

CVE-2026-18819 is a cross-site request forgery (CSRF) vulnerability affecting RackTables versions up to and including 0.22.0. The vulnerability allows remote attackers to perform unauthorized actions by exploiting the lack of CSRF protection in the affected versions. The vulnerability has been publicly disclosed, but no official fix or patch has been confirmed by the project maintainer.

References

Community reviews

Loading reviews…