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 77805 weak executable signature verification
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
High · CVSS 7.9CVE-2026-77805

Weak Executable Signature Verification Vulnerability in Progress® Telerik® Fiddler® ClassicCVE-2026-77805

Answer in brief

CVE-2026-77805 records a High severity (CVSS 7.9) vulnerability in Weak Executable Signature Verification Vulnerability in Progress® Telerik® Fiddler® Classic. The current sources do not mark it as known exploited. The current feed maps Progress Software/Progress® Telerik® Fiddler® Classic (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 5, 2026Updated Oct 5, 2026Source checked Oct 5, 2026First seen by HOL Oct 5, 2026Material review Oct 5, 2026
Upstream Advisory

Key facts

Risk
High · CVSS 7.9
Exploitation
Not marked as known exploited
Affected software
1 mapped package or product
Fix availability
Available

Why this deserves its current priority

CVSS is 7.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 Progress Software/Progress® Telerik® Fiddler® Classic (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Progress Software/Progress® Telerik® Fiddler® Classicgeneric>=1.0.0 <6.0.20262.100216.0.20262.10021

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for Progress Software/Progress® Telerik® Fiddler® Classic.
  2. 2Review the reported fix. Source-reported workaround: Carefully review every User Account Control elevation prompt raised by Fiddler Classic and confirm that it refers to the expected executable before approving it. Alternatively, avoid launching external tools from the Fiddler Classic application, such as the Windows 8 Loopback Exemptions tool or the machine store certificate trust tool.

Evidence timeline and material changes

  1. Published upstream

    Oct 5, 2026

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

    Oct 5, 2026

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

    Oct 5, 2026

Sources and claim methodology

  • Source referencedocs.telerik.com
Upstream source description

In Progress® Telerik® Fiddler® Classic for Windows, versions prior to v6.0.20262.10021, the integrity check applied to the external helper tools launched by the application is insufficient. Before executing a helper tool, the application only verifies that the file carries a valid Authenticode signature whose certificate subject name matches a broad allow list of publisher name fragments, rather than verifying that the file is the specific executable shipped with that version of the product. A local threat actor with low privileges who replaces one of these helper executables with any other validly signed binary from an allow-listed publisher can cause the substituted binary to be executed by the application, including with Administrator privileges for the tools that request elevation, resulting in privilege escalation and execution of unintended code. Successful exploitation requires the user to launch the affected external tool and to approve the elevation prompt without noticing that it refers to a different executable.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • HTTP Request Smuggling Vulnerability in Progress® Telerik® Fiddler® ClassicSame progress software/progress® telerik® fiddler® classic package
  • Front-end Desynchronization Vulnerability in Progress® Telerik® Fiddler® ClassicSame progress software/progress® telerik® fiddler® classic package
  • Time-of-check Time-of-use (TOCTOU) Race Condition in Root Certificate Installation in Progress® Telerik® Fiddler® ClassicSame progress software/progress® telerik® fiddler® classic package
  • WordPress Starter Templates plugin <= 4.7.7 - Cross Site Scripting (XSS) vulnerabilitySame generic ecosystem
  • WordPress Presto Player plugin <= 4.5.2 - Cross Site Scripting (XSS) vulnerabilitySame generic ecosystem
  • WordPress JS Help Desk plugin <= 4.0.0 - Insecure Direct Object References (IDOR) vulnerabilitySame generic ecosystem

Record context

Vulnerability class
Privilege Escalation
EPSS
Not reported
CWE IDs
CWE-347
Source
CVE List V5
Source checked
Oct 5, 2026
References
1 linked source
Open source record