Out-of-bounds read in Meta folly
Priority MEDIUM 46CWE-125Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA.
Summary
Improper handling of close_notify alerts can result in an out-of-bounds read in AsyncSSLSocket. This issue affects folly prior to v2019.11.04.00.
Why it matters now
EPSS 0.01744 77th percentileScored 2026-11-07
Fix Fixed folly (Facebook): v2019.11.04.00
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
Remediation
- Fix · CNA folly (Facebook) Fixed in v2019.11.04.00
Timeline
- 2026-10-02 Threatist record created from CVE-2019-11934
- 2026-10-03 Alias added: GHSA-87hj-px7p-jhf4
References
More Meta Folly vulnerabilities
- TI-2021-06352 Heap-based buffer overflow in Meta folly CVSS 3.1CRITICAL 9.8
- TI-2018-04662 Memory corruption in Meta HHVM CVSS 3.1HIGH 7.5
Sources
- CVE-2019-11934 · CVE Program
- CVE-2019-11934 · NVD
- FIRST EPSS
- GHSA-87hj-px7p-jhf4 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences