Little CMS (aka Little Color Management System) 2.9 has an integer overflow in the AllocateDataSet function in cmscgats.c, leading to a heap
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: 1.7% (FIRST EPSS); higher than 77.2% of all records.
- 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: lcms2 (Alpine:v3.10) 2.9-r1; lcms2 (Debian:12) 2.9-3; lcms2 (Debian:8) 2.6-3+deb8u2.
Low priority for now. Upgrade to lcms2 (Alpine:v3.10) 2.9-r1; lcms2 (Debian:12) 2.9-3; lcms2 (Debian:8) 2.6-3+deb8u2 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
Little CMS (aka Little Color Management System) 2.9 has an integer overflow in the AllocateDataSet function in cmscgats.c, leading to a heap-based buffer overflow in the SetData function via a crafted file in the second argument to cmsIT8LoadFromFile.
- Published
- Sep 3, 2018
- Updated
- Jun 16, 2026
- EPSS
- 1.7% · 77th percentile
- CWE
- CWE-190
Report tools
Action score
23
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.7%
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 |
|---|---|---|
| littlecms | little cms color engine | cpe:2.3:a:littlecms:little_cms_color_engine |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
| redhat | enterprise linux desktop | cpe:2.3:o:redhat:enterprise_linux_desktop |
| redhat | enterprise linux server | cpe:2.3:o:redhat:enterprise_linux_server |
| redhat | enterprise linux workstation | cpe:2.3:o:redhat:enterprise_linux_workstation |
| 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.
- canonical ubuntu linux12.04
- canonical ubuntu linux14.04
- canonical ubuntu linux16.04
- canonical ubuntu linux18.04
- debian debian linux8.0
- debian debian linux9.0
- littlecms little cms color engine2.9
- redhat enterprise linux desktop6.0
- redhat enterprise linux server6.0
- redhat enterprise linux workstation6.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | lcms2 | before 2.9-r1 | 2.9-r1 |
| Debian:12 | lcms2 | before 2.9-3 | 2.9-3 |
| Debian:8 | lcms2 | before 2.6-3+deb8u2 | 2.6-3+deb8u2 |
| Debian:9 | lcms2 | before 2.8-4+deb9u1 | 2.8-4+deb9u1 |
| openSUSE:Leap 15.0 | java-1_8_0-openjdk | before 1.8.0.191-lp150.2.9.2 | 1.8.0.191-lp150.2.9.2 |
| openSUSE:Tumbleweed | lcms2 | before 2.12-1.3 | 2.12-1.3 |
| Red Hat:rhel_extras:6 | chromium-browser | before 0:70.0.3538.67-1.el6_10 | 0:70.0.3538.67-1.el6_10 |
| Red Hat:rhel_extras:6 | chromium-browser-debuginfo | before 0:70.0.3538.67-1.el6_10 | 0:70.0.3538.67-1.el6_10 |
| SUSE:Linux Enterprise Desktop 12 SP3 | lcms2 | before 2.7-9.7.1 | 2.7-9.7.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 | lcms2 | before 2.9-3.3.1 | 2.9-3.3.1 |
| SUSE:Linux Enterprise Module for Legacy 15 | java-1_8_0-openjdk | before 1.8.0.191-3.13.1 | 1.8.0.191-3.13.1 |
| SUSE:OpenStack Cloud 7 | java-1_7_0-openjdk | before 1.7.0.201-43.18.1 | 1.7.0.201-43.18.1 |
| SUSE:OpenStack Cloud 7 | java-1_8_0-openjdk | before 1.8.0.191-27.29.1 | 1.8.0.191-27.29.1 |
Same product
littlecms: all recordsOther highest-scoring records for the same primary product.
- CVE-2013-7455Double free vulnerability in the DefaultICCintents function in cmscnvrt.c in liblcms2 in Little CMS 2.x before 2.6 allows remote attackers t41Plan
- CVE-2016-10165The Type_MLU_Read function in cmstypes.c in Little CMS (aka lcms2) allows remote attackers to obtain sensitive information or cause a denial29Monitor
- CVE-2013-4160Little CMS (lcms2) before 2.5, as used in OpenJDK 7 and possibly other products, allows remote attackers to cause a denial of service (NULL 21Monitor
- CVE-2013-4276Multiple stack-based buffer overflows in LittleCMS (aka lcms or liblcms) 1.19 and earlier allow remote attackers to cause a denial of servic18Monitor
- CVE-2026-42798Little CMS (lcms2) 2.16 through 2.18 before 2.19 has an integer overflow in ParseCube in cmscgats.c.16Monitor
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 |
|---|---|---|
| alpine:lcms2 | 2.9-r1 · Alpine:v3.10 | Package registry (OSV) |
| debian:lcms2 | 2.9-3 · Debian:12 | Package registry (OSV) |
| opensuse:java-1_8_0-openjdk | 1.8.0.191-lp150.2.9.2 · openSUSE:Leap 15.0 | Package registry (OSV) |
| opensuse:lcms2 | 2.12-1.3 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:chromium-browser | 0:70.0.3538.67-1.el6_10 · Red Hat:rhel_extras:6 | Package registry (OSV) |
| red hat:chromium-browser-debuginfo | 0:70.0.3538.67-1.el6_10 · Red Hat:rhel_extras:6 | Package registry (OSV) |
| suse:java-1_7_0-openjdk | 1.7.0.201-43.18.1 · SUSE:OpenStack Cloud 7 | Package registry (OSV) |
| suse:java-1_8_0-openjdk | 1.8.0.191-27.29.1 · SUSE:OpenStack Cloud 7 | Package registry (OSV) |
| suse:lcms2 | 2.9-3.3.1 · SUSE:Linux Enterprise Module for Basesystem 15 | 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
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-190 · Integer Overflow or WraparoundCVSS vector
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
nvd-primary
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 (6 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.