Skip to main content

Threats Tagged 'cve-2026-58380'

View all threats tagged with 'cve-2026-58380'. Filter and sort to focus on specific types of threats.

Pro Console Lifetime

Stop chasing alerts. Route them.

Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.

Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)

View Plans & Pricing

API access activates after upgrading in Console -> Billing.

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now

Filter Threats

Narrow down the results by type, severity, or affected countries

Search threats by title, CVE ID, or description. Maximum 100 characters.
Active filters (1):Tag: cve-2026-58380

Threats Tagged 'cve-2026-58380'

Click on any threat for detailed analysis and mitigation recommendations

0

These are all security issues fixed in the gimp-3.2.6-1.1 package on the GA media of openSUSE Tumbleweed.

Join the discussion
0

A stack buffer overflow vulnerability exists in GIMP's PNM file format parser due to an off-by-one error in the pnmscanner_gettoken() function. This flaw can cause memory corruption when processing specially crafted PNM files, potentially leading to denial of service or arbitrary code execution. Red Hat has issued a security update addressing this issue in GIMP for Red Hat Enterprise Linux 9.

Join the discussion
0

This security update for GIMP addresses three vulnerabilities: a heap buffer overflow in PSP file parsing (CVE-2026-58379), a buffer overflow in pnmscanner_gettoken (CVE-2026-58380), and a double-free issue with PSP layer names (CVE-2026-58381). These issues could lead to memory corruption and potential instability or exploitation. The update fixes these vulnerabilities to improve the security and stability of GIMP.

Join the discussion

A flaw was found in GIMP's PNM file format parser. When parsing a specially crafted PNM file, the pnmscanner_gettoken() function writes a null terminator one byte past the end of a stack-allocated buffer due to an off-by-one error in the loop boundary check. This could lead to memory corruption, potentially resulting in denial of service or arbitrary code execution.

Join the discussion

Showing 1 to 4 of 4 results

Filters:Tag: cve-2026-58380
Page 1 of 1
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses