Evidence used
- CISA confirms exploitation in the wild.
- A structured source references public exploit or proof-of-concept material.
- EPSS is 61.09% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2019
CVE-2019-5786High confidence
Google Chrome Blink Use-After-Free Vulnerability
Google · Chrome Blink
6.5MediumCVSS 3.1
Protect now
Fix not verifiedCISA confirms exploitation in the wild and lists 2022-06-13 as the remediation due date.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Critical, raised 2 bands.upgradedsince 23 May 2022
Compensating controls
- Restrict the affected network interface to trusted sources where business-safe.
- Increase monitoring for the attack path and post-exploitation behaviour described in the report.
Verification
- Confirm that the asset runs Google Chrome Blink and falls inside the recorded affected range.
- Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Distribution package intelligence
7 package statesRelease-specific package status
Alpine, Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Alpine v3.23v3.23 · community | chromium | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 72.0.3626.121-r0 | Alpine Security Database ↗Source updated 22 Oct 2026 |
| Alpine v3.22v3.22 · community | chromium | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 72.0.3626.121-r0 | Alpine Security Database ↗Source updated 22 Oct 2026 |
| Alpine v3.21v3.21 · community | chromium | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 72.0.3626.121-r0 | Alpine Security Database ↗Source updated 22 Oct 2026 |
| Debian trixietrixie · source | chromium | Vendor fix publishedDebian records a fixed source-package version for this release. | 72.0.3626.121-1 | Debian Security Tracker ↗Source updated 23 Oct 2026 |
| Debian bookwormbookworm · source | chromium | Vendor fix publishedDebian records a fixed source-package version for this release. | 72.0.3626.121-1 | Debian Security Tracker ↗Source updated 23 Oct 2026 |
| Debian forkyforky · source | chromium | Vendor fix publishedDebian records a fixed source-package version for this release. | 72.0.3626.121-1 | Debian Security Tracker ↗Source updated 23 Oct 2026 |
| Debian sidsid · source | chromium | Vendor fix publishedDebian records a fixed source-package version for this release. | 72.0.3626.121-1 | Debian Security Tracker ↗Source updated 23 Oct 2026 |
Open-source package ranges1 source-attributed range
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| npmpuppeteer | < 1.13.0 | 1.13.0 | GitHub advisory ↗github reviewed aggregator · 11 Nov 2023 |
CISA confirms exploitation in the wild and lists 2022-06-13 as the remediation due date.
Fix not verified01
What, why and how
Google Chrome Blink contains a heap use-after-free vulnerability that allows an attacker to potentially perform out of bounds memory access via a crafted HTML page.
What
Google Chrome Blink contains a heap use-after-free vulnerability that allows an attacker to potentially perform out of bounds memory access via a crafted HTML page.
Why
The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.
How
An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
Google Chrome Blink contains a heap use-after-free vulnerability that allows an attacker to potentially perform out of bounds memory access via a crafted HTML page.
Why
The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.
How
An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation Confirmed in the wild
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.CISA added this CVE to its Known Exploited Vulnerabilities catalogue on 2022-05-23.
Public PoC / exploit material Reference recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.
- Likely attack path
- a network path → Use After Free → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- Required interaction required
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-416 ↗
CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix not verified
- Affected
- Chrome: unspecified < 72.0.3626.121
- Fixed
- No fixed version is explicitly recorded in the structured CVE data.
- Action
- No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 27 Jun 2019 · Last source change 21 Oct 2025, 23:45 UTC · CWE-416 · Use After Free
CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
EPSS source FIRST · tracked since 2026-09-01
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2020-0957
Product sourceCISA KEV
Remediation sourceCVE/CNA references
CWE sourceCISA ADP
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- ENISA known-exploited stateENISA EUVD now records this CVE in its known-exploited dataset.ENISA EUVD ↗
- Before
- not listed in ENISA EUVD known-exploited dataset
- After
- listed in ENISA EUVD known-exploited dataset (EUVD-2020-0957)
- ENISA EUVD mappingEUVD-2020-0957 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2020-0957"}
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- unspecified < 72.0.3626.121 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- Chrome: unspecified < 72.0.3626.121 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: chromereleases.googleblog.com/stable-channel-update-for-desktop.html.chromereleases.googleblog.com ↗
- Before
- no authoritative guidance recorded
- After
- vendor advisory: chromereleases.googleblog.com/stable-channel-update-for-desktop.html
- Public exploit evidencePublic exploit evidence changed from No public exploit to Public exploit reference.crbug.com ↗
- Before
- No public exploit
- After
- Public exploit reference
- CVSS scoreCVSS scoring authority changed from CISA ADP to NIST NVD; the displayed base score remained 6.5.NIST NVD ↗
- Before
- 6.5 (CVSS 3.1 · CISA ADP · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H)
- After
- 6.5 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H)
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.