Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-82641 – Unauthenticated TLS Key Exposure – Keploy 3.1.0 through 3.6.25

Be the first to know when new zero-days emerge:

Summary

CVE-2026-82641 is a missing-authentication vulnerability (CWE-306) affecting Keploy, an open-source API testing and traffic-recording tool. The agent’s control-plane HTTP server binds without any authentication mechanism, allowing an unauthenticated network attacker to retrieve live TLS session keys and manipulate active recording sessions. The vulnerability has a CVSS v3.1 base score of 8.6 and a CVSS v4.0 base score of 8.8 (High).

Technical details

  • Root cause: The Keploy agent’s control-plane HTTP server (pkg/agent/routes/server.go) is started with fmt.Sprintf(":%d", port), which binds to all network interfaces (0.0.0.0) instead of loopback only, and none of its endpoints require credentials.
  • Trigger conditions: The agent must be running with its control-plane HTTP server active (native mode, or Docker mode where the port is published as 0.0.0.0:<AgentPort>), leaving it reachable from other local processes or, in Docker deployments, from network peers.
  • Attack vector: Network (AV:N) — no privileges or user interaction required (PR:N/UI:N).
  • Exploitable endpoints:
    • GET /agent/pcap/keylog — streams live NSS keylog lines to any unauthenticated subscriber, generated as the agent MITM-proxies application HTTPS/database connections.
    • POST /agent/stop — allows an attacker to unilaterally terminate an active recording session.
    • POST /agent/storemocks — allows an attacker to inject or overwrite captured mock data.
  • Impact: By subscribing to the keylog stream while capturing traffic via /agent/pcap/traffic, an attacker can fully decrypt recorded TLS sessions (e.g., with Wireshark), exposing sensitive application and database traffic. The exposed control endpoints also allow disruption of active test recordings and tampering with mock data used in downstream testing.

Affected software

  • Keploy (go.keploy.io/server/v3) versions 3.1.0 through 3.6.25 (inclusive).

Severity

  • CVSS v3.1: 8.6 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
  • CVSS v4.0: 8.8 (High) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade to a patched Keploy version that includes fix commit a6257d2b3184b85eb30edad345464aa292297b83, which binds the native-mode agent control server to 127.0.0.1 only and restricts Docker port publishing to the host’s loopback interface (127.0.0.1:port:port) rather than all interfaces.
  • If unable to patch immediately:
    • Ensure the Keploy agent’s control-plane port is not published or exposed beyond the local host (avoid 0.0.0.0 bindings in Docker deployments).
    • Restrict network access to hosts running Keploy agents using host-based firewalls or network segmentation, allowing only trusted local processes to reach the agent port.
    • Audit any environments where Keploy agents are running to confirm the control-plane port is not reachable from untrusted networks or shared multi-tenant hosts.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge