Skip to content
VulniPulse
Advisory severityHigh8.8Red Hat Linux

High [CVE-2026-63649] Privilege escalation via arbitrary configuration file loading

This high-severity Red Hat Linux advisory covers CVE-2026-63649.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-63649 Source published Source updated

VulniPulse record published Record updated

Affected products & platforms
Red Hat LinuxUnclassified
Open source advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

The Windows interactive service in OpenVPN 2.4.0 through 2.6.21 and 2.7_alpha1 through 2.7.5 allows local authenticated users to bypass the trusted configuration directory constraint and load arbitrary configuration files via crafted options that bypass whitelist checks This bypass allows the user to load arbitrary configuration files, which could lead to privilege escalation or other system compromise.

This Important vulnerability affects the Windows interactive service of OpenVPN, allowing a local authenticated user to bypass configuration file restrictions and achieve privilege escalation.

This issue is specific to OpenVPN deployments on Microsoft Windows and does not directly impact Red Hat products, which primarily utilize OpenVPN on Linux-based systems. Red Hat severity: Important — CVSS 8.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H).

Weakness: CWE-22.

Affected versions
  • 2.4.0
  • 2.6.21
  • 2.7.5

Official advisory · high-confidence parse· fetched 24 days ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 24 days ago·verify at source

Mitigation

The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.

Official advisory · high-confidence parse· fetched 24 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.