Skip to main content
Menu
CVEs

AsiaInfo International Business Support System unauthenticated admin access via management API

CVE-2026-125297Published November 10, 2026, updated

9.3CriticalCNA
Exploited
No known exploitation
Fix
Fixed in Business Support System 9.2.41 · aether-menu 2.2.7
Who is exposed
Not reported

Summary

AsiaInfo Business Support System (BSS) is affected by a missing-authentication flaw in its management API. Remotely, without logging in, an attacker could create a new account with administrative privileges, take over existing accounts, or carry out other administrative actions.

Written by a model

Original description

AsiaInfo Business Support System (BSS) 9.2.0 through 9.2.40 accepts unauthenticated requests via the management API '/bss/sysmgnt/api/'. A remote, unauthenticated attacker could provision a new account with administrative privileges or take over existing accounts, and perform other administrative actions. Fixed in 9.2.41.

Who should check

Teams running AsiaInfo BSS Platform 9.2.0 through 9.2.40 or aether-menu 2.2.1 through 2.2.6, such as telecom subscriber-management operators

“AsiaInfo BSS Platform 9.2.0 through 9.2.40 (component aether-menu 2.2.1 through 2.2.6)”

github.com

What to do

Upgrade to a fixed version: Business Support System 9.2.41 · aether-menu 2.2.7.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-125297 (AsiaInfo Business Support System (BSS) Missing Authentication), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-125297 (entry last updated 2026-11-17):
Affected:
- AsiaInfo International Business Support System: from 9.2.0, fixed in 9.2.41
- AsiaInfo International aether-menu: from 2.2.1, fixed in 2.2.7
Fixed versions: 9.2.41, 2.2.7.
Conditions (all must be true for the bug to be hit):
- Affected AsiaInfo BSS Platform 9.2.0 through 9.2.40, with aether-menu 2.2.1 through 2.2.6 (source: https://github.com/trevorkaon/vulnerability-security-research/blob/main/advisories/asiainfo/CVE-2026-125297.md)
- Management API service carries no authorization policy tag, so the mesh authorizer does not cover it (source: https://github.com/trevorkaon/vulnerability-security-research/blob/main/advisories/asiainfo/CVE-2026-125297.md)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-125297 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125297 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.asiainfo.eu/cloudbss
- https://github.com/trevorkaon/vulnerability-security-research/blob/main/advisories/asiainfo/CVE-2026-125297.md
- https://www.cve.org/CVERecord?id=CVE-2026-125297
- https://raw.githubusercontent.com/cisagov/CSAF/develop/csaf_files/IT/white/2026/va-26-313-03.json
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-125297
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-125297"}.

Affected versions

cve.now Index

30of 100 · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.3, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 35 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now7 days
  4. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: total

  5. Record last updated

Public exploit activity

100%0Posted on X by cve.nowNov 10Nov 22
  • EPSS: 0.77%
  • Posted on X by cve.now Nov 10

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Evidence 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Linkasiainfo.eu · cloudbss
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-125297
RecordNVD · CVE-2026-125297
Other links 2
AdvisoryGitHub · trevorkaon/vulnerability-security-research · Advisory CVE-2026-125297.md
Linkraw.githubusercontent.com · cisagov/CSAF/develop/csaf_files/IT/white/2026/va-26-313-03.json

Questions about CVE-2026-125297

Is CVE-2026-125297 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

The management API service has no authorization policy tag, so the mesh authorizer does not cover it. Without credentials, the management plane can be fully compromised, including takeover of platform accounts (including administrators), creation of privileged operators, and disclosure of the user directory and API consumer secrets.

Source: github.com

Which versions are affected by CVE-2026-125297?

Business Support System: from 9.2.0 before 9.2.41. aether-menu: from 2.2.1 before 2.2.7.

Source: cve.now feed data

Am I affected, and how do I check?

Versions AsiaInfo BSS Platform 9.2.0 through 9.2.40 are affected, and the aether-menu component versions 2.2.1 through 2.2.6 are affected. To check, look at the installed BSS Platform version and the aether-menu component version in that installation.

Source: github.com

How do I fix CVE-2026-125297?

Upgrade to a fixed version: Business Support System 9.2.41 · aether-menu 2.2.7. The vendor's advisory also recommends AsiaInfo BSS Platform 9.2.41 or aether-menu 2.2.7 or later.

Source: cve.now feed data, github.com

No corrections so far. Something wrong on this page? Report an error.