CVE-2018-18385: Asciidoctor in versions < 1.5.8 allows remote attackers to cause a denial of service (infinite loop)
CVE-2018-18385 is a high-severity flaw (CVSS 7.5) affecting asciidoctor. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Asciidoctor in versions < 1.5.8 allows remote attackers to cause a denial of service (infinite loop). The loop was caused by the fact that Parser.next_block was not exhausting all the lines in the reader as the while loop expected it would. This was happening because the regular expression that detects any list was not agreeing with the regular expression that detects a specific list type. So the line kept getting pushed back onto the reader, hen
Why this priority
- High severity
- Public exploit reference
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 7.5 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 2.2% (top 17%) |
| CISA exploited list | No |
| Weakness | CWE-835 |
| Published | 2018-10-16 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2018-18385?
asciidoctor: upgrade to 1.5.8. Exact commands for each OS are on this page.
Is CVE-2018-18385 being exploited?
CVE-2018-18385 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2018-18385 affect?
CVE-2018-18385 affects asciidoctor. Severity is high (CVSS 7.5). Asciidoctor in versions < 1.5.8 allows remote attackers to cause a denial of service (infinite loop). The loop was caused by the fact that Parser.next_block was not exhausting all the lines in the reader as the while loop expected it would.
How urgent is CVE-2018-18385?
Priority 57/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action