Quick answers
- Is CVE-2026-68539 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-68539 being exploited in the wild.
- How severe is CVE-2026-68539?
- High severity, with a CVSS score of 7.5, published 11 November 2026.
- Which products and versions are affected?
- Fulgur-Rs Fulgur 0.4.4 to before 0.29.0.
- Is there a fix for CVE-2026-68539?
- Yes: fixed in 0.29.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-68539 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-68539?
- Check whether you run Fulgur-Rs Fulgur at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 0.29.0
Technical details
The vulnerability is a denial-of-service caused by unbudgeted accumulation of CSS string-set named-string values in the StringSetPass component. When processing CSS, the library accumulated per-element snapshots of named-string values with no memory limit, allowing an attacker to amplify a small crafted document into large retained memory and CPU overhead. The fix introduces memory budgets (MAX_STRING_SNAPSHOT_BYTES) to bound string-set snapshot storage and running-map memory consumption.
Affected products
- fulgur-rs fulgur 0.4.4 to before 0.29.0
Timeline
- 2026-11-11: disclosed
- 2026-07-06: patched