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 6232 out of bounds write in lr11xx transceiver
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 5.2CVE-2026-6232

Out-of-bounds write in LR11xx TransceiverCVE-2026-6232

Answer in brief

CVE-2026-6232 records a Medium severity (CVSS 5.2) vulnerability in Out-of-bounds write in LR11xx Transceiver. The current sources do not mark it as known exploited. The current feed maps Semtech/LR1110 Modem-e (generic), Semtech/LR1110 Transceiver (generic), Semtech/LR1120 Transceiver (generic), Semtech/LR1121 Modem-e (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.

Analysis pending evidence review

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

Published Oct 12, 2026Updated Oct 12, 2026Source checked Oct 12, 2026First seen by HOL Oct 12, 2026Material review Oct 12, 2026
Upstream Advisory

Key facts

Risk
Medium · CVSS 5.2
Exploitation
Not marked as known exploited
Affected software
5 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 5.2. 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 Semtech/LR1110 Modem-e (generic), Semtech/LR1110 Transceiver (generic), Semtech/LR1120 Transceiver (generic), Semtech/LR1121 Modem-e (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Semtech/LR1110 Modem-egeneric>=0 <2.1.12.1.1
Semtech/LR1110 Transceivergeneric>=0 <0x04030x0403
Semtech/LR1120 Transceivergeneric>=0 <0x02030x0203
Semtech/LR1121 Modem-egeneric>=0 <2.1.12.1.1
Semtech/LR1121 Transceivergeneric>=0 <0x01050x0105

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for Semtech/LR1110 Modem-e, Semtech/LR1110 Transceiver, Semtech/LR1120 Transceiver.
  2. 2Review the reported fix. Update Semtech/LR1110 Modem-e to 2.1.1; Semtech/LR1110 Transceiver to 0x0403; Semtech/LR1120 Transceiver to 0x0203; Semtech/LR1121 Modem-e to 2.1.1; Semtech/LR1121 Transceiver to 0x0105 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Oct 12, 2026

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

  2. Source modified

    Oct 12, 2026

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

  3. First seen by HOL

    Oct 12, 2026

Sources and claim methodology

  • Source referencesemtech.com
Upstream source description

An out-of-bounds write vulnerability in the SPI host command interface of Semtech's LR11xx transceiver firmware where a crafted SPI host command with an oversized length field can cause the firmware to write up to 254 arbitrary bytes past the bounds of an internal, non-persistent memory buffer. Exploitation requires physical access to the device and logical access to the SPI bus.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • OOB Read/Write via Negative Array Index in exllamav3_ext Kernel TableAlso CWE-787
  • Out-of-bounds write in Progress MarkLogic ServerAlso CWE-787
  • Path traversal in Gleam via unvalidated package application namesSame generic ecosystem
  • WordPress Salevo plugin <= 1.3.0 - Broken Access Control vulnerabilitySame generic ecosystem
  • copyparty FTP: upload outside defined volumes (limited path traversal)Same generic ecosystem
  • hex_core decompresses registry and Erlang term API responses without size limitsSame generic ecosystem

Record context

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