HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members

Guard product

  • Guard overviewLocal security and control for AI agents and the tools they use.
  • FeaturesRuntime protection, policy routing, review, and evidence.

Explore Guard

  • Product previewWalk through Guard surfaces in read-only demo mode.
  • ComparisonCompare Guard with native controls and AI security vendors.

AI tools

  • All AI toolsEvery supported AI tool and how Guard applies policy to it.
  • Codex
  • Claude Code
  • Cursor
  • Antigravity CLI
  • OpenCode
  • Hermes
  • OpenClaw
  • GitHub Copilot CLI
  • Antigravity
  • Kimi
  • Grok
  • Pi / Oh My Pi
  • Zcode

Extensions

  • All extensionsBrowse command and MCP coverage with owners and stated limits.
  • Command coverageShell command protection across clouds, databases, backups, and packages.
  • MCP server coverageSee how Guard maps risk state across MCP tools and servers.
  • Core safetyThe safety floor listings that ship with Guard.
  • Data and resilienceBackup and storage command protection.
  • Cloud and infrastructureAWS, Azure, GCP, Kubernetes, and more.

Security

  • AI security hubSecurity research, advisories, and agent safety coverage.
  • AI tool securitySecurity profiles for each supported coding agent.
  • Safe labsHands-on attack simulations with safe boundaries.
  • Redacted warningsReal blocked actions with sensitive details removed.
  • AdvisoriesCoordinated disclosure reports for AI tooling.
  • Active CVEsSearch active CVEs affecting AI tooling.

Learn

  • Security guidesPractical guides for securing AI agent workflows.
  • DocsInstall, configure, and operate Guard with confidence.
  • ResearchPublished security research, benchmarks, and methodology.

Community

  • ReleasesVersion history, shipped changes and upgrade notes.
  • ContributorsThe people and contributions behind HOL Guard.
  • AffiliatesShare Guard with your audience and earn from referrals.
  • SponsorKeep agent security open: sponsor a project, place a banner, or fund a security initiative.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 81893 gdk pixbuf gdk pixbuf invalid write in jpeg icc
HOL Guard

Public security guidance for teams protecting AI harnesses, MCP servers, skills, prompts, and local tool execution.

Install Guard

AI Security

  • Prompt injection
  • MCP security
  • OWASP MCP mapping
  • Supply chain

Resources

  • Trust packet
  • Harness setup
  • Redacted warnings
  • Safe labs

Product

  • Install Guard
  • Pricing
  • Open dashboard
Guard
  • Guard Overview
  • Releases
  • Contributors
  • Install Guard
  • Pricing
Docs
  • Documentation Index
  • Developer Hub
  • API Reference
  • Root OpenAPI
  • Registry OpenAPI
  • Run in Postman
  • Standards
  • Submit ERC-8004 Contract
  • Feature Your Agent
Best Plugins
  • Browse Plugins
  • Plugin Launches
  • Best Claude Plugins
  • Best Codex Plugins
  • Best Grok Plugins
  • Best Kimi Plugins
  • Best DeepSeek Plugins
  • Best Antigravity Plugins
  • Best MCP Servers
  • Best Cursor Plugins
  • Best OpenCode Plugins
Best Agents
  • Best ERC-8004 Agents
  • Best Virtuals Agents
  • Best MCP Servers
  • Best A2A Agents
  • Best x402 Payable
  • All Categories
Community
  • Telegram
  • X
More
  • About HOL
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
Medium · CVSS 4.7CVE-2026-81893

Gdk-pixbuf: gdk-pixbuf: invalid write in jpeg icc profile parser on error recoveryCVE-2026-81893

Answer in brief

CVE-2026-81893 records a Medium severity (CVSS 4.7) vulnerability in Gdk-pixbuf: gdk-pixbuf: invalid write in jpeg icc profile parser on error recovery. The current sources do not mark it as known exploited. The current feed maps Red Hat/gdk-pixbuf2 (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 27, 2026Updated Aug 28, 2026Source checked Oct 11, 2026First seen by HOL Aug 27, 2026Material review Aug 28, 2026
Upstream Advisory

Key facts

Risk
Medium · CVSS 4.7
Exploitation
Not marked as known exploited
Affected software
1 mapped package or product
Fix availability
Not reported

Why this deserves its current priority

CVSS is 4.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Red Hat/gdk-pixbuf2 (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Red Hat/gdk-pixbuf2generic*Not reported

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for Red Hat/gdk-pixbuf2.
  2. 2Review the reported fix. Source-reported workaround: Avoid opening or automatically indexing untrusted JPEG images with applications linked against a vulnerable gdk-pixbuf version until an updated package is installed.

Evidence timeline and material changes

  1. Published upstream

    Aug 27, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  2. Source modified

    Aug 28, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  3. First seen by HOL

    Aug 27, 2026

Sources and claim methodology

  • Source referenceaccess.redhat.com
  • Source referencebugzilla.redhat.com
  • Source referencegitlab.gnome.org
  • Source referencegitlab.gnome.org
Upstream source description

A flaw was found in gdk-pixbuf. When loading a specially crafted JPEG image containing chunked ICC profile markers, an error during ICC profile parsing can leave stale size metadata after the profile buffer is freed. A subsequent allocation in the same decode can cause an out-of-bounds write, potentially crashing the application. To exploit this flaw, an application using gdk-pixbuf must process the malicious JPEG image. Affected version >= 2.26.4

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • Stack out-of-bounds write in the Goodix GT911 touch controller driver from an unvalidated device-reported touch point countAlso CWE-787
  • Unbounded variable-length array in fuel gauge syscall verifiers allows kernel stack overflow from user modeAlso CWE-787
  • Out-of-bounds write in the NXP MCUX TRNG entropy driver for non-word-multiple request lengthsAlso CWE-787
  • Channel tokens and organization API key exposed in API responsesSame generic ecosystem
  • zhayujie CowAgent Web Console upload read denial of serviceSame generic ecosystem
  • zhayujie CowAgent Media Download memory allocationSame generic ecosystem

Record context

Vulnerability class
Memory Corruption
EPSS
Not reported
CWE IDs
CWE-787
Source
CVE List V5
Source checked
Oct 11, 2026
References
4 linked sources
Open source record