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 102812 hardcoded aes 128 key and fixed iv in
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.9CVE-2026-102812

Hardcoded AES-128 Key and Fixed IV in Configuration Backup Encryption in TP-Link RE305 and Archer C7CVE-2026-102812

Answer in brief

CVE-2026-102812 records a Medium severity (CVSS 6.9) vulnerability in Hardcoded AES-128 Key and Fixed IV in Configuration Backup Encryption in TP-Link RE305 and Archer C7. The current sources do not mark it as known exploited. The current feed maps TP-Link Systems Inc./Archer C7 v5 (generic), TP-Link Systems Inc./RE305 v3 (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 Oct 27, 2026Updated Oct 27, 2026Source checked Oct 27, 2026First seen by HOL Oct 27, 2026Material review Oct 27, 2026
Upstream Advisory

Key facts

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

Why this deserves its current priority

CVSS is 6.9. 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 TP-Link Systems Inc./Archer C7 v5 (generic), TP-Link Systems Inc./RE305 v3 (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
TP-Link Systems Inc./Archer C7 v5generic>=0 <1.3.1 Build 20260821 Rel. 412561.3.1 Build 20260821 Rel. 41256, 1.3.1
TP-Link Systems Inc./RE305 v3generic>=0 <1.1.8 Build 20260921 Rel. 428531.1.8 Build 20260921 Rel. 42853, 1.1.8

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for TP-Link Systems Inc./Archer C7 v5, TP-Link Systems Inc./RE305 v3.
  2. 2Review the reported fix. Update TP-Link Systems Inc./Archer C7 v5 to 1.3.1 Build 20260821 Rel. 41256; TP-Link Systems Inc./RE305 v3 to 1.1.8 Build 20260921 Rel. 42853 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Oct 27, 2026

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

  2. Source modified

    Oct 27, 2026

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

  3. First seen by HOL

    Oct 27, 2026

Sources and claim methodology

  • Source referencetp-link.com
  • Source referencetp-link.com
  • Source referencetp-link.com
  • Source referencetp-link.com
  • Source referencetp-link.com
Upstream source description

A hard-coded cryptographic key vulnerability exists in the user-configuration backup mechanism of TP-Link RE305 V3 and Archer C7 V5. A fixed AES-128 key and initialization vector are embedded in the firmware configuration-management component. An attacker who obtains an affected configuration backup file may extract the cryptographic material from the firmware and use it to decrypt the backup.  Successful exploitation may disclose sensitive configuration information contained in a backup file, including administrator passwords and Wi-Fi credentials.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • Administrator Password Reset Through the Verification-Code Interface in TP-Link RE305Same tp-link systems inc./re305 v3 package
  • Improper Authentication in TP-Link TDDP v2 Allows Root Command Execution in TP-Link RE305Same tp-link systems inc./re305 v3 package
  • Command Injection in tmpServer Allows Local Privilege Escalation in TP-Link RE305Same tp-link systems inc./re305 v3 package
  • Unauthenticated Wireless Regulatory Region Configuration in TP-Link RE305Same tp-link systems inc./re305 v3 package

Record context

Vulnerability class
Secret Exfiltration
EPSS
Not reported
CWE IDs
CWE-321
Source
CVE List V5
Source checked
Oct 27, 2026
References
5 linked sources
Open source record