CVE-2026-50593: Graphite before 1.3.15 has an integer underflow and resultant out-of-bounds write via Graphite actions, because slotat does not ensure that
Noroxi assessment
Priority: Monitor (action score 29/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.11% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: Graphite project Graphite 1.3.15.
Low priority for now. Upgrade to Graphite project Graphite 1.3.15 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
Graphite before 1.3.15 has an integer underflow and resultant out-of-bounds write via Graphite actions, because slotat does not ensure that an offset is within the allowed slot-map range.
- Published
- Jun 5, 2026
- Updated
- Jul 23, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- CWE-191
Report tools
Action score
29
Monitor
Low priority for now.
- CVSS
- 29 / 40 · 7.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · mitre
- 7.3
- NVD has not scored this yet; the score shown is the CNA’s.
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.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (mitre). Independent of NVD's CPE analysis and usually ahead of it.
Graphite project Graphite
- before 1.3.15affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | graphite2 | before 1.3.14-1+deb12u1 | 1.3.14-1+deb12u1 |
| Debian:13 | graphite2 | before 1.3.14-2+deb13u1 | 1.3.14-2+deb13u1 |
| Debian:14 | graphite2 | before 1.3.15-2 | 1.3.15-2 |
| openSUSE:Leap 16.0 | graphite2 | before 1.3.14-160000.3.1 | 1.3.14-160000.3.1 |
| openSUSE:Tumbleweed | graphite2 | before 1.3.15-1.1 | 1.3.15-1.1 |
| SUSE:Linux Enterprise Micro 5.3 | graphite2 | before 1.3.11-150000.4.6.1 | 1.3.11-150000.4.6.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | graphite2 | before 1.3.14-150600.3.3.1 | 1.3.14-150600.3.3.1 |
| SUSE:Linux Enterprise Module for Package Hub 15 SP7 | libreoffice | before 26.2.5.1-150500.20.37.1 | 26.2.5.1-150500.20.37.1 |
| SUSE:Linux Enterprise Server 12 SP5-LTSS | graphite2 | before 1.3.1-10.6.1 | 1.3.1-10.6.1 |
| SUSE:Linux Enterprise Server 16.0 | graphite2 | before 1.3.14-160000.3.1 | 1.3.14-160000.3.1 |
| SUSE:Linux Micro 6.0 | graphite2 | before 1.3.14-4.1 | 1.3.14-4.1 |
| SUSE:Linux Micro 6.1 | graphite2 | before 1.3.14-slfo.1.1_2.1 | 1.3.14-slfo.1.1_2.1 |
Same product
graphite project: all recordsOther highest-scoring records for the same primary product.
- CVE-2013-5093The renderLocalView function in render/views.py in graphite-web in Graphite 0.9.5 through 0.9.10 uses the pickle Python module unsafely, whi40Plan
- CVE-2017-18638send_email in graphite-web/webapp/graphite/composer/views.py in Graphite through 1.1.5 is vulnerable to SSRF.35Monitor
- CVE-2013-5942Graphite 0.9.5 through 0.9.10 uses the pickle Python module unsafely, which allows remote attackers to execute arbitrary code via a crafted 28Monitor
Published before and after this one in the same product
- ← EarlierCVE-2022-4728Dec 27, 2022 · Graphite Web Cookie cross site scripting21Monitor
- ← EarlierCVE-2022-4729Dec 27, 2022 · Graphite Web Template Name cross site scripting21Monitor
- ← EarlierCVE-2022-4730Dec 27, 2022 · Graphite Web Absolute Time Range cross site scripting21Monitor
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 |
|---|---|---|
| Graphite project Graphite | 1.3.15 | Vendor (CNA) |
| debian:graphite2 | 1.3.14-1+deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:graphite2 | 1.3.15-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:graphite2 | 1.3.14-4.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:libreoffice | 26.2.5.1-150500.20.37.1 · SUSE:Linux Enterprise Module for Package Hub 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 with local access to the system can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-191 · Integer Underflow (Wrap or Wraparound)CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:H
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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
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.