ZDF
Sign inSign up

Vulnerabilities

Vulnerability · GHSA-rw63-4hw9-p4v7

OpenVPN Client Export Utility users can export private keys for unlisted certificate refs

Published Jul 21, 2026 · catalog updated Jul 21, 2026 · OpenVPN Client Export Utility

Last checked Nov 2, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for GHSA-rw63-4hw9-p4v7. A missing EPSS score is not a low risk. Compare OpenVPN Client Export Utility with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (OpenVPN Client Export Utility).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
Medium5.9
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Version ranges on file
Affected products
composer opnsense/core

### Summary OPNsense Core's OpenVPN Client Export API accepts a route-supplied in the download endpoint without verifying that the certificate is present in the selected OpenVPN server's account/certificate allowlist. An authenticated user with only the permission can request an unlisted certificate reference and receive an exported configuration containing the private key. ### Details The affected module is . looks up the selected OpenVPN server and lists only certificate references where ; this is the account/certificate list exposed to the frontend. instead accepts directly from the URL route, calls , and copies the returned and values into and . then writes into the exported block, while the archive and Viscosity exporters package the same private key into PKCS#12 files. The download endpoint does not repeat the allowlist check and does not verify that the certificate belongs to the selected server CA, the current user, or any export-visible account row. This issue has been safely reproduced with positive and negative controls on a 26.1.6-series environment and on the official 26.7.r1 build. This is a project-owned object-authorization issue, not a dependency CVE, weak credential, or non-default deployment problem. Public OPNsense advisories already cover OpenVPN status-view XSS/RCE, OpenVPN Client Specific Override path traversal, and Trust CA/Certificate XPath oracle secret extraction; this issue uses a different entry point and permission boundary because it only requires OpenVPN Client Export Utility access and does not require CA/Certificate Manager access or XPath injection. ### PoC The examples below use as the target placeholder. Prerequisites: an OpenVPN server exists; its exportable account/certificate list does not include the target certificate ; the target certificate exists in the system trust store and has a private key; the attacker account has only the permission. Negative control 1: an unauthenticated request cannot obtain the JSON account/cert

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • composer opnsense/core<= 26.7

How to fix GHSA-rw63-4hw9-p4v7

  • Upgrade

    GHSA-rw63-4hw9-p4v7 lists a fix boundary at 26.7. Compare the installed build with that boundary before you change production.

  • Version check

    Affected <= 26.7

  • Advisory

    Open the inventory_github record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for GHSA-rw63-4hw9-p4v7. A missing EPSS score is not a low risk. Compare OpenVPN Client Export Utility with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with <= 26.7. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-639: Authorization Bypass Through User-Controlled Key. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

OPNsense security

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Jul 21, 2026 · Maintainer security tabs

    Detected

    ### Summary OPNsense Core's OpenVPN Client Export API accepts a route-supplied in the download endpoint without verifying that the certificate is present in the selected OpenVPN server's account/certificate allowlist. An authenticated user with only the permission can request an unlisted certificate reference and receive an exported configuration containing the private key. ### Details The affecte

Sources

  • Maintainer security tabsVendor advisoryGHSA-rw63-4hw9-p4v7

    ### Summary OPNsense Core's OpenVPN Client Export API accepts a route-supplied in the download endpoint without verifying that the certificate is present in the selected OpenVPN server's account/certificate allowlist. An authenticated user with only the permission can request an unlisted certificate reference and receive an exported configuration containing the private key. ### Details The affecte

    github.com

Freshness

Last verified in this catalog Jul 21, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Maintainer security tabsNov 2, 2026