🛡️ CVE-2026-42798 on BellSoft — lcms2
Distribution advisory
This page covers CVE-2026-42798 as tracked by BellSoft, for the package lcms2. The fix is available in version 2.19-r0; earlier versions remain affected.
How this vulnerability can be exploited
This issue can be reached with local access to the system, attack complexity is high, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality low, integrity none, availability low.
Weakness class
BELL-CVE-2026-42798 is classified as CWE-190: Integer Overflow or Wraparound. Arithmetic produces a value too large for its type and wraps around, so a later size or bounds check passes when it should not.
Affected software
BELL-CVE-2026-42798 is recorded against 1 package.
- lcms2 (from 2.16-r0 up to 2.19-r0)
Timeline and source
Published on 6 May 2026 and last revised on 8 May 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
CVE-2026-42798 on other distributions
Each distribution ships its own build and its own fixed version. Pick the one you run:
Details
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| lcms2 | 2.16-r0 | 2.19-r0 |
References
Similar Threats
- Unknown openSUSE-SU-2026:21202-1
- Unknown SUSE-SU-2026:22506-1
- Unknown MGASA-2026-0214
- Unknown SUSE-SU-2026:22070-1
- Medium OESA-2026-2325
Vulnerability Monitoring
Track new vulnerabilities in lcms2
BELL-CVE-2026-42798 is rated CVSS 4.0 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.
Set Up Free Alerts →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.