CVE-2026-81714

openssl_encrypt before 1.4.9 Plugin Signing Trust Anchor Enrollment Bypass

Published Aug 27, 2026 CVSS 4.0 · 9.3 Critical EPSS < 1% KEV · Not listed
Description
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).

Analysis

AI-generated

Technical impact

opens ssl_encrypt uses a suffix-tolerant fingerprint check when enrolling a plugin‑signing trust anchor. When an operator confirms a short, easily forgeable GPG key ID, the verifier accepts any key that shares the same trailing bits, allowing an attacker’s colliding key to be enrolled as trusted. Once enrolled, that key can sign malicious plugins, which the application will accept under the ENFORCE signature policy, effectively granting the attacker code execution rights. The weakness is a form of improper fingerprint verification, classified as CWE‑347.

Affected Systems

The vulnerability exists in the jahlives openssl_encrypt Python package versions 1.4.8 and earlier. Version 1.4.9 introduced strict matching of the full primary‑key fingerprint during enrollment, eliminating the suffix tolerance and thereby securing against this issue.

Risk and Exploitability

The CVSS score of 9.3 designates this a critical flaw. EPSS data is not available, and the vulnerability is not listed in the CISA KEV catalog. Exploitation is likely to be local or semi‑local, requiring an operator who can confirm the short key ID or an automated process that performs the confirmation. The attack vector is inferred from the description: an operator or automated installer might unknowingly enroll a colliding key. Mitigation by updating to 1.4.9 removes the risk entirely.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the openssl_encrypt package to version 1.4.9 or newer to enforce full primary‑key fingerprint matching during enrollment
  • If an upgrade is not immediately possible, block or log any enrollment attempts that use short GPG key IDs and demand confirmation of the complete fingerprint
  • Implement monitoring to detect unexpected additions to the trust‑anchor store and audit plugin signatures to ensure they match established, trusted keys

Generated by OpenCVE AI on August 27, 2026 at 18:44 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:jahlives:openssl_encrypt:*:*:*:*:*:*:*:*
Type Values Removed Values Added
CPEs cpe:2.3:a:jahlives:openssl_encrypt:*:*:*:*:*:python:*:*
Type Values Removed Values Added
First Time appeared Jahlives
Jahlives openssl Encrypt
Vendors & Products Jahlives
Jahlives openssl Encrypt
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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).
Title openssl_encrypt before 1.4.9 Plugin Signing Trust Anchor Enrollment Bypass
Weaknesses CWE-347
References
Metrics cvssV3_1

{'score': 7, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 9.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-347

    Improper Verification of Cryptographic Signature

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 1, 2026, 3:21 PM
Reserved
Aug 27, 2026, 11:13 AM
Status
Analyzed
Published
Aug 27, 2026, 5:21 PM
Modified
Sep 2, 2026, 1:09 PM