/

CVE-2026-74884

Severity:

HIGH RISK

(7.5)

Path Traversal (CWE-73) in openssl_encrypt Plugin Config

CVE-2026-74884

Analyzed

Vulnerability type

Category:

Path Traversal

CWE:

CWE-73

Impact:

Arbitrary directory access

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A path traversal vulnerability in openssl_encrypt allows a plugin identifier to influence the location used to build a plugin configuration directory path. If an attacker can control the plugin_id value, they may access directories outside the intended plugin location.

Affected context

The vulnerability occurs in openssl_encrypt implementations that use the plugin_id parameter to construct plugin configuration paths without first restricting or canonicalizing it. Risk is present when an attacker can submit or influence plugin identifiers and the resulting path is resolved with the application's filesystem permissions.

Exploit preconditions

  • Attack surface: Plugin configuration path handling
  • Required access: Ability to control or influence the plugin_id parameter
  • Trigger point: Construction and resolution of the plugin configuration directory path
  • Why exploitation is possible: Path components are accepted without sufficient sanitization or confinement to the designated plugin directory

Why this happens

The underlying bug is improper restriction of externally influenced path components. The _is_safe_path method uses plugin_id while constructing a filesystem path but does not adequately remove or reject traversal elements, allowing the resulting path to escape its intended base directory. This maps to CWE-73, External Control of File Name or Path, because input-controlled data affects filesystem path resolution without a reliable confinement check.

Potential impact

  • An attacker may access files or directories outside the intended plugin location
  • Sensitive configuration data could be exposed
  • Application behavior could be altered through unintended filesystem access
  • The impact could extend to other resources reachable by the process account

General mitigation guidance

Mitigation generally focuses on treating plugin identifiers as constrained

identifiers rather than filesystem path fragments.

Common defensive patterns include:

  • Allowing only an explicit, tightly defined identifier format
  • Rejecting path separators, traversal components, and unexpected encoding forms
  • Resolving candidate paths and verifying they remain beneath a fixed trusted directory
  • Using secure-by-default path-joining or sandboxing abstractions
  • Avoiding attacker-controlled names when selecting configuration resources
  • Applying least-privilege filesystem permissions to the service account
  • Keeping plugin configuration directories inaccessible to unnecessary processes

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis rules that flag external input used in filesystem path construction
  • Code review checks for path joins that lack canonicalization and base-directory validation
  • Tests covering encoded separators, alternate path representations, and boundary paths
  • Runtime monitoring for access attempts outside approved plugin directories
  • Policy enforcement requiring allowlisted plugin identifiers and constrained filesystem access
  • Automated security review tools that identify CWE-73 patterns in path-handling code

Sources

SourceLink
github.comgithub.com/jahlives/openssl_encrypt/security/advisories/GHSA-8jpj-w975-rwv5
vulncheck.comvulncheck.com/advisories/openssl-encrypt-before-path-traversal-via-plugin-id

Frequently asked

questions

It may be remotely exploitable when a network-facing component accepts an

attacker-controlled plugin_id and uses it to resolve configuration paths.

Otherwise, exploitation may require local or otherwise trusted access to the

plugin configuration interface.

The attacker generally needs the ability to influence the plugin_id value or

another input that reaches plugin configuration path construction. The

resulting impact is also limited by the filesystem permissions of the service.

Treat plugin identifiers as allowlisted logical names, reject path syntax, and

verify that every resolved path remains within the intended configuration

directory before accessing it.

Centralize secure path handling, apply least-privilege permissions, include

traversal-focused tests in CI, and enforce code-review policies for

input-controlled filesystem paths.

Find out what's already
exploitable in your codebase.