CVE-2026-23818
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 · uneditedA vulnerability has been identified in the graphical user interface (GUI) of HPE Aruba Networking Private 5G Core On-Prem that could allow an attacker to abuse an open redirect vulnerability in the login flow using a crafted URL. Successful exploitation may redirect an authenticated user to an attacker-controlled server hosting a spoofed login page prompting the unsuspecting victim to give away their credentials, which could then be captured by the attacker, before being redirected back to the legitimate login page.
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 confidenceAn open redirect vulnerability exists in the GUI login flow of HPE Aruba Networking Private 5G Core On-Prem. Attackers can craft malicious URLs that redirect authenticated users to an attacker-controlled server hosting a spoofed login page, enabling credential theft via phishing before redirecting users back to the legitimate login page.
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< 1.25.3.1CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
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.
-
Check installed product versionAccess the system CLI or administrative console and retrieve the HPE Aruba Networking Private 5G Core version information. Common methods include running 'show version' or checking the About/System Info section in the web GUI.Affected if The installed version is lower than 1.25.3.1
-
Verify GUI login interface is enabledConfirm that the web-based GUI login interface is accessible and not disabled. Check system settings or configuration for GUI/HTTP access controls.Affected if The GUI login interface is enabled and reachable from network segments where users authenticate
-
Inspect login redirect behaviorAttempt to access the login page with a custom redirect parameter (such as ?next= or ?redirect=) pointing to an external domain. Observe whether the application accepts and follows the redirect to an external URL before the login completes.Affected if The application allows arbitrary external URLs as redirect targets in the login flow without validation or warning
A user is affected if the installed HPE Aruba Networking Private 5G Core version is below 1.25.3.1 AND the GUI login interface is enabled, allowing unauthenticated or authenticated users to be redirected to attacker-controlled domains via the login flow.
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 · scoped1.25.3.1
Apply vendor patches when available; meanwhile, implement URL filtering/monitoring for outbound connections and educate users about phishing threats. Consider disabling external redirects in the login flow if configuration options exist.
1.25.3.1
- Download HPE Aruba Networking Private 5G Core version 1.25.3.1 or later from the HPE support portal (support.hpe.com)
- Review the upgrade documentation and release notes for version 1.25.3.1
- Create a backup of the current configuration before proceeding with the upgrade
- Schedule a maintenance window to minimize disruption
- Follow the documented upgrade procedure specific to Aruba Networking Private 5G Core to apply the update
- After upgrade, verify the system is functioning correctly and the GUI is accessible
- Confirm the version number has been updated to 1.25.3.1 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23818 — 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-23818 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