Skip to main content
CVE-2024-37826VulnerabilityPublished Updated

CVE-2024-37826: serva · n/a

Affects servaSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.2% chance of exploitation in 30 days – higher than 69% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Aug 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
GitHubvercot/servapkg:github/vercot/servaOther threatsAffected
  • =4.6.0
Fixed in–

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

AI-suggested

1. Restrict network access to vercot Serva instances by implementing firewall rules or network segmentation to limit exposure to untrusted networks. 2. Monitor HTTP traffic to detect and block anomalous or malformed requests that could trigger the NULL pointer dereference. 3. Employ intrusion detection or prevention systems (IDS/IPS) with signatures or heuristics targeting suspicious HTTP requests against vercot Serva. 4. If possible, temporarily disable or limit the use of affected vercot Serva services until an official patch or update is released. 5. Engage with the vendor or community to obtain patches or updates as soon as they become available and apply them promptly. 6. Conduct regular backups and develop incident response plans to quickly recover from potential DoS incidents. 7. Review and harden application code or configurations if custom deployments or integrations exist to mitigate NULL pointer dereference risks. 8. Maintain up-to-date asset inventories to identify all instances of vercot Serva and prioritize remediation efforts accordingly.

Description

A NULL pointer dereference in vercot Serva v4.6.0 allows attackers to cause a Denial of Service (DoS) via a crafted HTTP request.

References

Community reviews

Loading reviews…