HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members
  • Sponsor HOL
  • Advertise with HOL

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.
  • SponsorFund agreed research, implementation and shared testing through the HOL Partner Program.
  • AdvertiseCompare README logo placements, previews and monthly prices, or promote a plugin or extension.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 23414 tls purge asynchold in tlsdecryptasyncwait
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
  • Contribute to HOL
  • Telegram
  • X
More
  • About HOL
  • Sponsor
  • Advertise
  • Affiliate program
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
High · CVSS 7.5CVE-2026-23414

tls: Purge async_hold in tls_decrypt_async_wait()CVE-2026-23414

Answer in brief

CVE-2026-23414 records a High severity (CVSS 7.5) vulnerability in tls: Purge async_hold in tls_decrypt_async_wait(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (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 Apr 2, 2026Updated Oct 19, 2026Source checked Nov 4, 2026First seen by HOL Jul 14, 2026Material review Oct 19, 2026
Upstream Advisory

Key facts

Risk
High · CVSS 7.5
Exploitation
Not marked as known exploited
Affected software
20 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 7.5. 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 Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.

Affected products and reported versions
ProductAffected versionsFixed versions
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:6.18:-:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.0:rc4:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.0:rc5:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.0:rc6:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.0:rc7:*:*:*:*:*:*Not reportedNot reported
Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=9f83fd0c179e0f458e824e417f9d5ad53443f685 <ac435be7c7613eb13a5a8ceb5182e10b50c9ce87 || >=c61d4368197d65c4809d9271f3b85325a600586a <2dcf324855c34e7f934ce978aa19b645a8f3ee71 || >=39dec4ea3daf77f684308576baf483b55ca7f160 <6dc11e0bd0a5466bcc76d275c09e5537bd0597dd || >=b8a6ff84abbcbbc445463de58704686011edc8e1 <9f557c7eae127b44d2e863917dc986a4b6cb1269 || >=b8a6ff84abbcbbc445463de58704686011edc8e1 <fd8037e1f18ca5336934d0e0e7e1a4fe097e749d || >=b8a6ff84abbcbbc445463de58704686011edc8e1 <84a8335d8300576f1b377ae24abca1d9f197807f || 4fc109d0ab196bd943b7451276690fb6bb48c2e0 || >=6.1.158 <6.1.168 || >=6.6.114 <6.6.131 || >=6.12.55 <6.12.80 || >=6.17.5 <6.18ac435be7c7613eb13a5a8ceb5182e10b50c9ce87, 2dcf324855c34e7f934ce978aa19b645a8f3ee71, 6dc11e0bd0a5466bcc76d275c09e5537bd0597dd, 9f557c7eae127b44d2e863917dc986a4b6cb1269, fd8037e1f18ca5336934d0e0e7e1a4fe097e749d, 84a8335d8300576f1b377ae24abca1d9f197807f, 6.1.168, 6.6.131, 6.12.80, 6.18
Linux/Linuxgeneric6.18Not reported
Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFPgeneric>=V3.1.6 <**
Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFPgeneric>=V3.1.5 <**
Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFPgeneric>=V3.1.7 <**
Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFPgeneric>=V3.1.6 <**
Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFPgeneric>=V3.1.5 <**
Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFPgeneric>=V3.1.7 <**
Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFPgeneric>=V3.1.6 <**
Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFPgeneric>=V3.1.5 <**
Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFPgeneric>=V3.1.7 <**

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux, Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP.
  2. 2Review the reported fix. Update Linux/Linux to ac435be7c7613eb13a5a8ceb5182e10b50c9ce87; Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP to *; Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP to *; Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP to *; Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP to *; Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP to *; Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP to *; Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFP to *; Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFP to *; Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFP to * if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Apr 2, 2026

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

  2. Source modified

    Oct 19, 2026

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

  3. First seen by HOL

    Jul 14, 2026

Sources and claim methodology

  • Source referencecert-portal.siemens.com
  • Source referencecert-portal.siemens.com
  • Source referencecert-portal.siemens.com
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
Upstream source description

In the Linux kernel, the following vulnerability has been resolved: tls: Purge async_hold in tls_decrypt_async_wait() The async_hold queue pins encrypted input skbs while the AEAD engine references their scatterlist data. Once tls_decrypt_async_wait() returns, every AEAD operation has completed and the engine no longer references those skbs, so they can be freed unconditionally. A subsequent patch adds batch async decryption to tls_sw_read_sock(), introducing a new call site that must drain pending AEAD operations and release held skbs. Move __skb_queue_purge(&ctx->async_hold) into tls_decrypt_async_wait() so the purge is centralized and every caller -- recvmsg's drain path, the -EBUSY fallback in tls_do_decryption(), and the new read_sock batch path -- releases held skbs on synchronization without each site managing the purge independently. This fixes a leak when tls_strp_msg_hold() fails part-way through, after having added some cloned skbs to the async_hold queue. tls_decrypt_sg() will then call tls_decrypt_async_wait() to process all pending decrypts, and drop back to synchronous mode, but tls_sw_recvmsg() only flushes the async_hold queue when one record has been processed in "fully-async" mode, which may not be the case here. [[email protected]: added leak comment]

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • Apache ActiveMQ, ActiveMQ Broker: Repeated rejected temporary destination consumer requests can lead to broker OOMAlso CWE-401

Record context

Vulnerability class
Vulnerability
EPSS
Not reported
CWE IDs
CWE-401
Source
CVE List V5
Source checked
Nov 4, 2026
References
9 linked sources
Open source record