Evidence used
- CISA confirms exploitation in the wild.
- EPSS is 11.01% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2024
CVE-2024-4761High confidence
Google Chromium V8 Out-of-Bounds Memory Write Vulnerability
Google · Chromium V8
8.8HighCVSS 3.1
Mitigate now
Mitigation availableCISA confirms exploitation in the wild and lists 2024-06-06 as the remediation due date.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:Critical, raised one band.upgradedsince 16 May 2024
Compensating controls
- Apply the linked authoritative mitigation while planning the permanent fix.
- 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 Chromium V8 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 | qt5-qtwebengine | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 5.15.17-r2 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.22v3.22 · community | qt5-qtwebengine | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 5.15.17-r2 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.21v3.21 · community | qt5-qtwebengine | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 5.15.17-r2 | Alpine Security Database ↗Source updated 19 Aug 2026 |
| Debian trixietrixie · source | chromium | Vendor fix publishedDebian records a fixed source-package version for this release. | 124.0.6367.207-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | chromium | Vendor fix publishedDebian records a fixed source-package version for this release. | 124.0.6367.207-1~deb12u1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | chromium | Vendor fix publishedDebian records a fixed source-package version for this release. | 124.0.6367.207-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | chromium | Vendor fix publishedDebian records a fixed source-package version for this release. | 124.0.6367.207-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
CISA confirms exploitation in the wild and lists 2024-06-06 as the remediation due date.
Mitigation available01
What, why and how
Google Chromium V8 Engine contains an unspecified out-of-bounds memory write vulnerability via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.
What
Google Chromium V8 Engine contains an unspecified out-of-bounds memory write vulnerability via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.
Why
A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.
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 Chromium V8 Engine contains an unspecified out-of-bounds memory write vulnerability via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.
Why
A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.
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 2024-05-16.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Out-of-bounds Write → 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-787 ↗
CWE-787: Out-of-bounds Write. The product writes data past the end, or before the beginning, of the intended buffer.
- 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:H/I:H/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.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.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. - Mitigation available
- Action
- The Cyber Centre encourages users and administrators to review the provided web link and apply the necessary updates.
- 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 14 May 2024 · Last source change 20 Dec 2025, 04:55 UTC · CWE-787 · Out-of-bounds Write
CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2024-44358
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
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: cyber.gc.ca/microsoft-edge-security-advisory-av24-270.chromereleases.googleblog.com ↗
- Before
- remediation: cyber.gc.ca/microsoft-edge-security-advisory-av24-270 · vendor advisory: chromereleases.googleblog.com/stable-channel-update-for-desktop_13.html
- After
- vendor advisory: chromereleases.googleblog.com/stable-channel-update-for-desktop_13.html
- Remediation statusRemediation status changed from Mitigation available to Awaiting fix.chromereleases.googleblog.com ↗
- Before
- Mitigation available
- After
- Awaiting fix
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- 124.0.6367.207 < 124.0.6367.207 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- Chrome: 124.0.6367.207 < 124.0.6367.207 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- Remediation statusRemediation status changed from Awaiting fix to Mitigation available.Canadian Centre for Cyber Security ↗
- Before
- Awaiting fix
- After
- Mitigation available
CVE published
Added to CISA KEV
Remediation guidance recorded
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.