CVE-2026-3563
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper input validation in the apps and endpoints configuration in PowerShell Universal before 2026.1.4 allows an authenticated user with permissions to create or modify Apps or Endpoints to override existing application or system routes, resulting in unintended request routing and denial of service via a conflicting URL path.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceImproper input validation in PowerShell Universal's apps and endpoints configuration allows authenticated users with create/modify permissions to override existing application or system routes, causing unintended request routing and potential denial of service through conflicting URL paths.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2026.1.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed PowerShell Universal versionRun 'Get-Module -ListAvailable PowerShellUniversal' or check the PowerShell Universal dashboard for the version numberAffected if The installed version is earlier than 2026.1.4
-
Determine if Apps and Endpoints configuration is in useReview the PowerShell Universal dashboard or configuration files for any defined Apps or EndpointsAffected if Apps or Endpoints have been created in the environment
-
Check for non-administrator users with create/modify permissionsReview role-based access control settings in PowerShell Universal to identify users or groups granted create/modify permissions on Apps and EndpointsAffected if Any authenticated user aside from trusted administrators has create or modify permissions for Apps or Endpoints
-
Inspect for conflicting route configurationsCompare defined App and Endpoint URL paths against system reserved routes and look for overlapping or shadowed pathsAffected if Any App or Endpoint route conflicts with existing application or system routes
Your environment is affected if you are running PowerShell Universal version earlier than 2026.1.4 with Apps or Endpoints that non-administrator users can modify, creating potential route conflicts.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2026.1.4
Upgrade to PowerShell Universal 2026.1.4 or later. As a compensating control, restrict the ability to create or modify Apps and Endpoints to only trusted administrators.
2026.1.4
- 1. Back up your current PowerShell Universal configuration and data
- 2. Download PowerShell Universal version 2026.1.4 or later from the official source
- 3. Stop the PowerShell Universal service
- 4. Install the updated version following standard upgrade procedures
- 5. Verify that existing apps and endpoints function correctly after upgrade
- 6. Test that the input validation prevents route override attempts
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3563 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-3563 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data