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 2023 6129 poly1305 mac implementation corrupts vector
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
  • Sponsor
  • Advertise
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
Medium · CVSS 6.5CVE-2023-6129

POLY1305 MAC implementation corrupts vector registers on PowerPCCVE-2023-6129

Answer in brief

CVE-2023-6129 records a Medium severity (CVSS 6.5) vulnerability in POLY1305 MAC implementation corrupts vector registers on PowerPC. The current sources do not mark it as known exploited. The current feed maps OpenSSL/OpenSSL (generic), Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystem (generic), Siemens/SINEC NMS (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 Jan 9, 2024Updated Oct 14, 2026Source checked Oct 14, 2026First seen by HOL Oct 14, 2026Material review Oct 14, 2026
Upstream Advisory

Key facts

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

Why this deserves its current priority

CVSS is 6.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 OpenSSL/OpenSSL (generic), Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystem (generic), Siemens/SINEC NMS (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
OpenSSL/OpenSSLgeneric>=3.2.0 <3.2.1 || >=3.1.0 <3.1.5 || >=3.0.0 <3.0.133.2.1, 3.1.5, 3.0.13
Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystemgeneric>=0 <V1.1.1V1.1.1
Siemens/SINEC NMSgeneric>=0 <V3.0 SP1V3.0 SP1, V3.0

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for OpenSSL/OpenSSL, Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystem, Siemens/SINEC NMS.
  2. 2Review the reported fix. Update OpenSSL/OpenSSL to 3.2.1; Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystem to V1.1.1; Siemens/SINEC NMS to V3.0 SP1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Jan 9, 2024

    Evidence: source:cvelist:source_dates:source-dates:record
  2. Source modified

    Oct 14, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  3. First seen by HOL

    Oct 14, 2026

Sources and claim methodology

  • Source referencecert-portal.siemens.com
  • Source referencecert-portal.siemens.com
  • Source referencecert-portal.siemens.com
  • Source referencecert-portal.siemens.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • Source referencesecurity.netapp.com
  • Source referencesecurity.netapp.com
  • Source referencesecurity.netapp.com
  • Source referencesecurity.netapp.com
  • Source referenceopenssl.org
  • Source referenceopenwall.com
Upstream source description

Issue summary: The POLY1305 MAC (message authentication code) implementation contains a bug that might corrupt the internal state of applications running on PowerPC CPU based platforms if the CPU provides vector instructions. Impact summary: If an attacker can influence whether the POLY1305 MAC algorithm is used, the application state might be corrupted with various application dependent consequences. The POLY1305 MAC (message authentication code) implementation in OpenSSL for PowerPC CPUs restores the contents of vector registers in a different order than they are saved. Thus the contents of some of these vector registers are corrupted when returning to the caller. The vulnerable code is used only on newer PowerPC processors supporting the PowerISA 2.07 instructions. The consequences of this kind of internal application state corruption can be various - from no consequences, if the calling application does not depend on the contents of non-volatile XMM registers at all, to the worst consequences, where the attacker could get complete control of the application process. However unless the compiler uses the vector registers for storing pointers, the most likely consequence, if any, would be an incorrect result of some application dependent calculations or a crash leading to a denial of service. The POLY1305 MAC algorithm is most frequently used as part of the CHACHA20-POLY1305 AEAD (authenticated encryption with associated data) algorithm. The most common usage of this AEAD cipher is with TLS protocol versions 1.2 and 1.3. If this cipher is enabled on the server a malicious client can influence whether this AEAD cipher is used. This implies that TLS server applications using OpenSSL can be potentially impacted. However we are currently not aware of any concrete application that would be affected by this issue therefore we consider this a Low severity security issue.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • Insufficient Authorization and User Boundary Validation in Omada Controller MSPSame generic ecosystem
  • Improper Authorization in TP-Link Omada Controller TLS Certificate and Private Key Management APISame generic ecosystem
  • Password Reset Code Accessible in User Listing APISame generic ecosystem
  • Praat Model Loader whisper.cpp whisper_model_load out-of-bounds writeSame generic ecosystem
  • qs.stringify with arrayFormat comma throws TypeError on array elements that cannot be coerced to a stringSame generic ecosystem
  • FreeRDP 3.0.0 before 3.32.0 Null Pointer Dereference via rdpsnd FragmentSame generic ecosystem

Record context

Vulnerability class
Missing Auth
EPSS
Not reported
CWE IDs
CWE-440
Source
CVE List V5
Source checked
Oct 14, 2026
References
13 linked sources
Open source record