CVE
SoftBank Air Terminal 6 root command execution in web management console
Affects SoftBank Corp. Air Terminal 6 firmware v1.01.80 and earlier, where a user who can log in to the web management console can run commands as root.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Air Terminal 6 firmware v1.01.80 and earlier
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 1.03% · 64th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 18/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
An OS command injection flaw in SoftBank Corp.'s Air Terminal 6 lets a user who can log in to the product's web management console run arbitrary commands with root privileges. The attacker must be on an adjacent network and needs low-level login access.
Read the original description
An OS command Injection issue exists in Air Terminal 6 provided by SoftBank Corp. Arbitrary commands may be executed with the root privilege by a user who can log in to the web management console of the affected product.
Who should check
Owners and administrators of SoftBank Air Terminal 6 devices running firmware v1.01.80 or earlier
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity8/10CVSS 8.0
- No patch5/5No patch listed yet
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 28 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Air Terminal 6 firmware v1.01.80 and earlierWorkaround: No fix is listed in the available facts. Limiting who can log in to the web management console reduces the exposure, since that login is what the flaw requires.
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-101107 (An OS command Injection issue exists in Air Terminal 6 provided by SoftBank Corp.), 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-101107 (entry last updated 2026-11-12):
Affected:
- SoftBank Corp. Air Terminal 6: through v1.01.80
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Air Terminal 6 firmware v1.01.80 and earlier (source: https://jvn.jp/en/jp/JVN64740097/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: adjacent access, low-privilege login, no user action.
CISA KEV: CVE-2026-101107 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-101107 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://jvn.jp/en/jp/JVN64740097/
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-101107
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-101107"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- SoftBank Corp. Air Terminal 6
through v1.01.80
Evidence 3
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-101107
Is CVE-2026-101107 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?
An OS command injection flaw lets a user who can log in to the web management console run arbitrary commands with root privilege on the device.Source: jvn.jp
Which versions are affected by CVE-2026-101107?
Air Terminal 6: through v1.01.80.Source: cve.now feed data
Am I affected, and how do I check?
Air Terminal 6 firmware v1.01.80 and earlier are affected. To check a device, compare its firmware version against v1.01.80.Source: jvn.jp
How do I fix CVE-2026-101107?
The available facts name no fixed firmware version or patch IDs, so check SoftBank Corp.'s advisory for a fix before taking action.Source: jvn.jp
What if there's no patch?
No fix is listed in the available facts. Limiting who can log in to the web management console reduces the exposure, since that login is what the flaw requires.Source: jvn.jp