CVE-2026-81714 Vulnerability Analysis & Exploit Details

CVE-2026-81714
Vulnerability Scoring

7.0
/10
High Risk

If left unpatched, CVE-2026-81714 could lead to major system disruptions or data loss.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Local
    Vulnerability requires local system access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: Required
    User interaction is necessary for successful exploitation.

CVE-2026-81714 Details

Status: Analyzed

Last updated: 🕐 02 Sep 2026, 13:09 UTC
Originally published on: 🕔 27 Aug 2026, 17:21 UTC

Time between publication and last update: 5 days

CVSS Release: version 3

CVSS3 Source

disclosure@vulncheck.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

CVE-2026-81714 Vulnerability Summary

CVE-2026-81714: openssl_encrypt (pip: openssl-encrypt) versions <= 1.4.8 use suffix-tolerant fingerprint matching in enroll_trust_key when binding a plugin-signing trust anchor. An operator who confirms a short (forgeable, ~32-bit) GPG key id could unknowingly enroll an attacker's colliding key as a trusted anchor, which then vouches for malicious plugins under the ENFORCE signature policy. Version 1.4.9 fixes this by requiring the confirmed value to exactly match the full primary-key fingerprint (case-insensitive, whitespace-stripped).

Assessing the Risk of CVE-2026-81714

Access Complexity Graph

The exploitability of CVE-2026-81714 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-81714

CVE-2026-81714 presents a challenge to exploit due to its high attack complexity, but the absence of privilege requirements still makes it a viable target for skilled attackers. A thorough security review is advised.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-81714, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-81714, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2026-81714 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2026-81714 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2026-81714 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2026-81714 References

External References

CWE Common Weakness Enumeration

CWE-347

CAPEC Common Attack Pattern Enumeration and Classification

  • Padding Oracle Crypto Attack CAPEC-463 An adversary is able to efficiently decrypt data without knowing the decryption key if a target system leaks data on whether or not a padding error happened while decrypting the ciphertext. A target system that leaks this type of information becomes the padding oracle and an adversary is able to make use of that oracle to efficiently decrypt data without knowing the decryption key by issuing on average 128*b calls to the padding oracle (where b is the number of bytes in the ciphertext block). In addition to performing decryption, an adversary is also able to produce valid ciphertexts (i.e., perform encryption) by using the padding oracle, all without knowing the encryption key.
  • Signature Spoofing by Improper Validation CAPEC-475 An adversary exploits a cryptographic weakness in the signature verification algorithm implementation to generate a valid signature without knowing the key.

Vulnerable Configurations

  • cpe:2.3:a:jahlives:openssl_encrypt:0.2.2:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:0.2.2:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:0.2.3:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:0.2.3:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:0.2.4:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:0.2.4:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:0.2.5:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:0.2.5:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:0.2.6:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:0.2.6:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:0.3.0:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:0.3.0:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:0.3.1:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:0.3.1:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:0.3.2:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:0.3.2:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:0.3.3:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:0.3.3:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:0.4.0:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:0.4.0:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:0.4.1:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:0.4.1:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:0.4.2:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:0.4.2:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:0.4.3:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:0.4.3:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:0.4.4:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:0.4.4:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:0.5.0:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:0.5.0:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:0.5.1:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:0.5.1:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:0.5.3:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:0.5.3:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:0.6.0:rc1:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:0.6.0:rc1:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:0.7.0:rc2:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:0.7.0:rc2:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:0.7.1:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:0.7.1:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:0.7.2:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:0.7.2:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:0.8.0:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:0.8.0:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:0.8.1:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:0.8.1:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:0.8.2:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:0.8.2:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:0.9.2:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:0.9.2:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.0.0:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.0.0:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.0.1:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.0.1:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.0.2:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.0.2:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.0.3:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.0.3:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.1.0:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.1.0:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.2.0:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.2.0:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.2.1:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.2.1:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.3.0:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.3.0:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.3.1:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.3.1:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.3.2:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.3.2:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.3.3:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.3.3:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.3.4:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.3.4:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.3.5:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.3.5:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.3.6:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.3.6:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.4.0:-:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.4.0:-:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.4.0:beta3:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.4.0:beta3:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.4.0:beta4:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.4.0:beta4:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.4.0:beta5:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.4.0:beta5:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.4.0:beta6:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.4.0:beta6:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.4.0:beta7:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.4.0:beta7:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.4.0:beta8:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.4.0:beta8:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.4.1:-:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.4.1:-:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.4.1:rc1:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.4.1:rc1:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.4.1:rc2:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.4.1:rc2:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.4.2:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.4.2:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.4.3:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.4.3:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.4.4:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.4.4:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.4.5:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.4.5:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.4.6:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.4.6:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.4.7:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.4.7:*:*:*:*:python:*:*
  • cpe:2.3:a:jahlives:openssl_encrypt:1.4.8:*:*:*:*:python:*:*
    cpe:2.3:a:jahlives:openssl_encrypt:1.4.8:*:*:*:*:python:*:*

Protect Your Infrastructure against CVE-2026-81714: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-97652 – The WP Statistics – Simple, privacy-friendly Google Analytics alternative plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via ...
  • CVE-2026-95662 – Cross-Site Scripting vulnerability in the Repasat application. Successful exploitation of this vulnerability could allow an attacker to trick a use...
  • CVE-2026-94639 – improper handling of exceptional conditions, Allocation of resources without limits or throttling, Uncaught exception vulnerability in Apache Thrif...
  • CVE-2026-94635 – Allocation of resources without limits or throttling, Improper handling of length parameter inconsistency vulnerability in Apache Thrift Lua bindin...
  • CVE-2026-94634 – Allocation of resources without limits or throttling, Initialization of a resource with an insecure default vulnerability in Apache Thrift Python b...