# CVE-2026-24498: Information disclosure in ipTIME AX2004M

> Attackers can bypass authentication to expose sensitive information on ipTIME routers, requiring firmware upgrades to mitigate.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Feb 2026
- **Updated:** 27 Feb 2026
- **Also known as:** GHSA-cr8p-gx5g-wjgh

## What is CVE-2026-24498?

CVE-2026-24498 is a medium-severity vulnerability in EFM-Networks, Inc. ipTIME AX2004M, published on 27 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Exposure of Sensitive Information to an Unauthorized Actor vulnerability in EFM-Networks, Inc. IpTIME T5008, EFM-Networks, Inc. IpTIME AX2004M, EFM-Networks, Inc. IpTIME AX3000Q, EFM-Networks, Inc. IpTIME AX6000M allows Authentication Bypass.This issue affects ipTIME T5008: through 15.26.8; ipTIME AX2004M: through 15.26.8; ipTIME AX3000Q: through 15.26.8; ipTIME AX6000M: through 15.26.8.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-24498?

It affects 4 products.


Products: Iptime Ax2004m Firmware, Iptime Ax3000q Firmware, Iptime Ax6000m Firmware, Iptime T5008 Firmware.

## How do I fix CVE-2026-24498?

No fix has been published for CVE-2026-24498 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-24498 being exploited?

There is no known exploitation of CVE-2026-24498 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24498 and fix it if it is affected.

What it is: CVE-2026-24498 is a medium-severity vulnerability in EFM-Networks, Inc. ipTIME AX2004M, published on 27 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-24498 in the wild and no public exploit code.

Affected product: EFM-Networks, Inc. ipTIME AX2004M. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-24498/ (Markdown: https://insights.sbomify.com/CVE-2026-24498/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24498
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24498
- OSV: https://osv.dev/vulnerability/CVE-2026-24498

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-24498/
Summaries are generated and may contain mistakes; the official description above is the record.