LiveActive security incident?Get immediate response
CVE Record

CVE-2026-3277: The OpenID Connect (OIDC) authentication configuration in PowerShell Universal before 2026.1.3 stores the...

The OpenID Connect (OIDC) authentication configuration in PowerShell Universal before 2026.1.3 stores the OIDC client secret in cleartext in the .universal/authentication.ps1 script, which allows an attacker with read access to that file to obtain the OIDC client credentials

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

PowerShell Universal versions before 2026.1.3 can store an OIDC login client secret in cleartext. If someone can read the authentication configuration file, they may steal that secret. This is mainly a confidentiality issue, not a direct remote takeover based on the provided sources.

Executive priority

Treat as a near-term remediation for affected OIDC deployments. The issue can expose authentication secrets, but available sources do not show active exploitation or direct remote compromise. Prioritize systems with broad local access, shared administration, or sensitive identity integrations.

Technical view

CVE-2026-3277 is CWE-312 cleartext storage of sensitive information in PowerShell Universal OIDC configuration. The secret is stored in .universal/authentication.ps1 before version 2026.1.3. CVSS 3.1 is 5.5: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N.

Likely exposure

Exposure is likely limited to PowerShell Universal deployments using OIDC authentication on versions before 2026.1.3. Risk depends on who can read .universal/authentication.ps1, including local users, service accounts, backups, or log collection paths.

Exploitation context

The provided sources do not indicate active exploitation, and the CVE is not listed as KEV. Exploitation requires read access to the configuration file. Stolen OIDC client credentials could affect authentication trust depending on the identity provider configuration.

Researcher notes

The source bundle names PowerShell Universal before 2026.1.3 and cleartext storage in .universal/authentication.ps1. The affected-version metadata is sparse, so confirm exact product version and vendor advisory details during triage. Do not assume exposure where OIDC is not enabled.

Mitigation direction

  • Upgrade PowerShell Universal to 2026.1.3 or later.
  • Rotate the affected OIDC client secret after upgrading.
  • Review file permissions for .universal/authentication.ps1.
  • Check Devolutions vendor guidance for any additional remediation.

Validation and detection

  • Identify PowerShell Universal instances and versions.
  • Confirm whether OIDC authentication is configured.
  • Check whether .universal/authentication.ps1 contains cleartext client secrets.
  • Review access controls and backups containing the authentication file.
  • Verify the OIDC client secret was rotated after remediation.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-312: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-3277 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N1.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2026-3277Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
DevolutionsPowerShell Universal0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-312 · source CWE mapping

Cleartext Storage of Sensitive Information

Cleartext Storage of Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.