{
  "id": "CVE-2026-81714",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-81714",
  "published_at": "2026-08-27T14:51:09.904Z",
  "title": "openssl_encrypt before 1.4.9 Plugin Signing Trust Anchor Enrollment Bypass",
  "vendor": "jahlives",
  "product": "openssl_encrypt",
  "cvss": {
    "score": 9.3,
    "source": "cna",
    "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"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "openssl_encrypt (pip: openssl-encrypt) versions \u003c= 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).",
  "cwe": "CWE-347",
  "cpes": [
    "cpe:2.3:a:jahlives:openssl_encrypt:*:*:*:*:*:python:*:*"
  ],
  "cvss_by_source": {
    "cna": 9.3
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "jahlives",
        "product": "openssl_encrypt",
        "ranges": [
          "\u003c 1.4.9"
        ],
        "fixed_in": [
          "1.4.9"
        ]
      }
    ],
    "upgrade": [
      "Upgrade openssl_encrypt to 1.4.9 or later."
    ],
    "references": [
      {
        "kind": "Vendor advisory",
        "url": "https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-xg52-638v-jc5m"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
