CVE-2021-48011

waiting for further signalsZero needs more public information before it can validate it.

EUVD-2021-34884 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
lukejacksonn servor >= 1.0.0, <= 4.0.2
CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
ETK-2026-1420Zero's internal tracking ID, independent of the CVE number., permanent identifier
8d 06h 51msince last run
1h 03mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h
0
+4h
+6h
+8h
+10h
+12h

description

Servor versions 1.0.0 through 4.0.2 are affected by a path traversal vulnerability. An unauthenticated remote attacker can access files and enumerate directories outside the configured served root through crafted request paths.

mitigation

Upgrade to a release newer than 4.0.2 if one is available and verify that encoded traversal sequences are rejected before path resolution. Until then, restrict access to the service and run it with minimal filesystem permissions.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.56%45th percentile
agent run time
1h 03m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-12 20:55Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-12 20:55Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2021-48011

{
  "etk_id": "ETK-2026-1420",
  "cve_id": "CVE-2021-48011",
  "display_id": "CVE-2021-48011",
  "ghsa_id": null,
  "euvd_id": "EUVD-2021-34884",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Path traversal in servor",
  "summary": "Servor versions 1.0.0 through 4.0.2 are affected by a path traversal vulnerability. An unauthenticated remote attacker can access files and enumerate directories outside the configured served root through crafted request paths.",
  "mitigation": "Upgrade to a release newer than 4.0.2 if one is available and verify that encoded traversal sequences are rejected before path resolution. Until then, restrict access to the service and run it with minimal filesystem permissions.",
  "vendor": "lukejacksonn",
  "product": "servor",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.0.0, <= 4.0.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "servor",
      "purl": null
    }
  ],
  "cwes": [
    22
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
  "epss_score": 0.0056,
  "epss_percentile": 0.4554,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 63.496081833333335,
  "t0_at": "2026-10-12T20:55:05.305000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-12T20:55:05.305000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-12T20:55:05.305000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2021-48011"
    }
  }
}

published 2026-10-12 21:51Z
last change 2026-10-21 04:45Z

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.