CVE Intelligence
Medium Info disclosure

CVE-2025-37160 — Authenticated Broken Access Control (BAC) in REST API Configuration Service

A broken access control (BAC) vulnerability in the web-based management interface could allow an authenticated remote attacker with low privileges to view sensitive information. Successful exploitation of this vulnerability could enable the attacker to disclose sensitive data.

Published Nov 18, 2025 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: hpe

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.3% (30-day exploitation probability)+3
  • Technical severity (medium)+3
  • Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.29%
ahead of 20% of scored CVEs · Oct 14, 2026
Affects
Hewlett Packard Enterprise (HPE)
HPE Aruba Networking AOS-CX and 1 more
CVSS base
6.5
Medium · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Hewlett Packard Enterprise (HPE) HPE Aruba Networking AOS-CX, Hpe Arubaos-cx).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes matching the vulnerability class (info disclosure), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Hewlett Packard Enterprise (HPE) HPE Aruba Networking AOS-CX ≥ 10.16.0000 and ≤ 10.16.1000≥ 10.15.0000 and ≤ 10.15.1020≥ 10.14.0000 and ≤ 10.14.1050≥ 10.13.0000 and ≤ 10.13.1090≥ 10.10.0000 and ≤ 10.10.1160 Vulnerable CVE Program (cve.org) e CISA ADP
Hpe Arubaos-cx ≥ 10.10.0000 and < 10.10.1170≥ 10.13.0000 and < 10.13.1101≥ 10.14.0000 and < 10.14.1060≥ 10.15.0000 and < 10.15.1030≥ 10.16.0000 and < 10.16.1001 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
6.5 CVSS 3.1 Medium 2.8 3.6 nvd@nist.gov via NIST National Vulnerability Database
5.3 CVSS 3.1 Medium 3.9 1.4 security-alert@hpe.com via NIST National Vulnerability Database
5.3 CVSS 3.1 Medium — — hpe via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N (score shown at the top: nvd@nist.gov)
Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 6.5 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-200 · Exposure of Sensitive Information

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.29%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Look for anomalous data read/export volumes and access to sensitive records.
web/proxy/WAF logsnetwork IDS/IPSapplication logsauthentication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · hewlett packard enterprise (hpe)/hpe aruba networking aos-cx
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • CVSS changed · 6.5
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • 2025
  • CVE published
    Nov 18, 2025 · hpe

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

1 on the record

Elsewhere on this site

Hewlett Packard Enterprise (HPE)
every CVE for this vendor
Info disclosure
same class
CWE-200
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-73783 Stack-based Buffer Overflow in Hpe Arubaos-cx Sep 1, 2026
  • CVE-2026-73782 Use of Externally-Controlled Format String in Hpe Arubaos-cx Sep 1, 2026
  • CVE-2026-73777 Improper Authentication in Hpe Arubaos-cx Sep 1, 2026
  • CVE-2026-73776 Improper Verification of Cryptographic Signature in Hpe Arubaos-cx Sep 1, 2026
  • CVE-2026-73775 Exposure of Sensitive Information in Hpe Arubaos-cx Sep 1, 2026
  • CVE-2026-73774 Classic Buffer Overflow in Hpe Arubaos-cx Sep 1, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-37160 is "Authenticated Broken Access Control (BAC) in REST API Configuration Service", rated Medium. It affects HPE Aruba Networking AOS-CX (Hewlett Packard Enterprise (HPE)); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.5 describes technical severity. EPSS 0.29% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.