CVE-2026-68538

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

GHSA-395p-pj7r-jm42 ↗EUVD-2026-124055 ↗

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.
fulgur-rs fulgur >= 0.15.0, < 0.27.0
fixed in 0.27.0
CWE-400 Uncontrolled Resource Consumption
ETK-2026-4226Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:cargo/fulgur
1h 41msince last run
30mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h10m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

fulgur versions 0.15.0 through 0.26.x can consume excessive CPU and memory while processing CSS counter content during document-to-PDF conversion. An attacker who can submit HTML or CSS to a service using fulgur may disrupt that service and other workloads sharing its host.

mitigation

Upgrade fulgur to version 0.27.0 or later. Until upgraded, restrict untrusted HTML and CSS submission to conversion services and enforce resource limits on conversion workers.

fixed in 0.27.0

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.
contextual
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.
–
agent run time
30m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-11 22:12Z
Δ 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

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-11 22:12Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-68538

{
  "etk_id": "ETK-2026-4226",
  "cve_id": "CVE-2026-68538",
  "display_id": "CVE-2026-68538",
  "ghsa_id": "GHSA-395p-pj7r-jm42",
  "euvd_id": "EUVD-2026-124055",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unbounded CSS counter expansion in fulgur",
  "summary": "fulgur versions 0.15.0 through 0.26.x can consume excessive CPU and memory while processing CSS counter content during document-to-PDF conversion. An attacker who can submit HTML or CSS to a service using fulgur may disrupt that service and other workloads sharing its host.",
  "mitigation": "Upgrade fulgur to version 0.27.0 or later. Until upgraded, restrict untrusted HTML and CSS submission to conversion services and enforce resource limits on conversion workers.",
  "vendor": "fulgur-rs",
  "product": "fulgur",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.15.0, < 0.27.0"
      ],
      "ecosystem": "rust",
      "fixed_versions": [
        "0.27.0"
      ],
      "package_name": "fulgur",
      "purl": "pkg:cargo/fulgur"
    }
  ],
  "cwes": [
    400
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 29.605695883333333,
  "t0_at": "2026-11-11T22:12:06.386000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-11T22:12:06.386000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-11T22:12:06.386000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-68538"
    }
  }
}

published 2026-11-11 22:52Z
last change 2026-11-12 00:37Z

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.