CVE-2025-0838: Heap Buffer overflow in Abseil
Noroxi assessment
Priority: Monitor (action score 23/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.62% (FIRST EPSS).
- Someone on the same network segment can trigger it. A low-privileged account is enough. Special conditions such as timing or configuration are required.
- Fixed version: abseil abseil-cpp 5a0e2cb5e3958dd90bb8569a2766622cb74d90c1.
Low priority for now. Upgrade to abseil abseil-cpp 5a0e2cb5e3958dd90bb8569a2766622cb74d90c1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
There exists a heap buffer overflow vulnerable in Abseil-cpp. The sized constructors, reserve(), and rehash() methods of absl::{flat,node}hash{set,map} did not impose an upper bound on their size argument. As a result, it was possible for a caller to pass a very large size that would cause an integer overflow when computing the size of the container's backing store, and a subsequent out-of-bounds memory write. Subsequent accesses to the container might also access out-of-bounds memory. We recommend upgrading past commit 5a0e2cb5e3958dd90bb8569a2766622cb74d90c1
- Published
- Feb 21, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.6% · 49th percentile
- CWE
- CWE-190
Report tools
Action score
23
Monitor
Low priority for now.
- CVSS
- 23 / 40 · 5.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Google
- 5.9
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:A/AC:H/AT:P/PR:L/UI:A/VC:L/VI:H/VA:L/SC:L/SI:H/SA:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| abseil | common libraries | cpe:2.3:a:abseil:common_libraries |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- abseil common librariesbefore 20250127.0
- debian debian linux11.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Google). Independent of NVD's CPE analysis and usually ahead of it.
abseil abseil-cpp
- before 5a0e2cb5e3958dd90bb8569a2766622cb74d90c1affected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | abseil | before 0~20200923.3-2+deb11u1 | 0~20200923.3-2+deb11u1 |
| Debian:12 | abseil | before 20220623.1-1+deb12u1 | 20220623.1-1+deb12u1 |
| Debian:13 | abseil | before 20240722.0-3 | 20240722.0-3 |
| openSUSE:Leap 15.6 | abseil-cpp | before 20240116.3-150600.19.6.1 | 20240116.3-150600.19.6.1 |
| openSUSE:Tumbleweed | abseil-cpp | before 20250814.0-2.1 | 20250814.0-2.1 |
| SUSE:Linux Enterprise Micro 5.3 | abseil-cpp | before 20230802.3-150400.10.7.1 | 20230802.3-150400.10.7.1 |
| SUSE:Linux Enterprise Micro 5.4 | abseil-cpp | before 20240116.3-150500.13.10.1 | 20240116.3-150500.13.10.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | abseil-cpp | before 20240116.3-150600.19.6.1 | 20240116.3-150600.19.6.1 |
| SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | abseil-cpp | before 20240116.3-8.6.1 | 20240116.3-8.6.1 |
| SUSE:Linux Micro 6.0 | abseil-cpp | before 20230802.3-1.1 | 20230802.3-1.1 |
| SUSE:Linux Micro 6.1 | abseil-cpp | before 20230802.3-slfo.1.1_1.1 | 20230802.3-slfo.1.1_1.1 |
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| abseil abseil-cpp | 5a0e2cb5e3958dd90bb8569a2766622cb74d90c1 | Vendor (CNA) |
| debian:abseil | 20220623.1-1+deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:abseil-cpp | 20240116.3-150600.19.6.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| suse:abseil-cpp | 20240116.3-150600.19.6.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- A low-privileged account is enough.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Adjacent
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- A
- Scope
- X
Weakness class (CWE)
CWE-190 · Integer Overflow or WraparoundCVSS vector
CVSS:4.0/AV:A/AC:H/AT:P/PR:L/UI:A/VC:L/VI:H/VA:L/SC:L/SI:H/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.