dbcve.org
T5008 FirmwareOperating system · Iptime

CVE-2026-24498

HIGH · 7.5 CVSS v3.1 Published 2026-02-27
Fix available
A fix is available. Upgrade to 15.27.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
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.

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 confidence

Multiple ipTIME router models (T5008, AX2004M, AX3000Q, AX6000M) contain an authentication bypass vulnerability that allows unauthorized actors to access sensitive information. The flaw exists in firmware versions through 15.26.8, enabling attackers to circumvent authentication controls on the device management interface.

MitigationApply vendor firmware update when available. Until then, restrict administrative interface access to trusted networks only, disable remote management if not required, and monitor for unauthorized access attempts.

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
T5008 FirmwareOperating system
Affected:< 15.27.2
Ax2004m FirmwareOperating system
Affected:< 15.27.2
Ax3000q FirmwareOperating system
Affected:< 15.27.2
Ax6000m FirmwareOperating system
Affected:< 15.27.2

CVSS 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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify ipTIME router model
    Access the router admin interface (typically 192.168.0.1) and check the device information or status page, or examine the physical device label
    Affected if The model is T5008, AX2004M, AX3000Q, or AX6000M
  2. Check installed firmware version
    In the router admin panel, navigate to System or Administration settings to find the firmware version information
    Affected if The firmware version is 15.26.8 or lower, or any version prior to 15.27.2
  3. Determine remote management exposure
    In the router settings, check Remote Management, WAN Access, or Administration settings to see if the web management interface is accessible from the internet
    Affected if Remote management is enabled and the admin interface is exposed to external networks
  4. Review logs for unauthorized access
    Check the router system logs or access logs for successful logins from unfamiliar IP addresses, unusual access patterns, or repeated authentication failures
    Affected if Logs show unauthorized access to the management interface from external IP addresses

The environment is affected if the device is an ipTIME T5008, AX2004M, AX3000Q, or AX6000M running firmware version 15.26.8 or below (any version below 15.27.2), especially if remote management is enabled

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 15.27.2 or later
Fixed in 15.27.2
Interim mitigation

Apply vendor firmware update when available. Until then, restrict administrative interface access to trusted networks only, disable remote management if not required, and monitor for unauthorized access attempts.

Recommended fix High confidence

Firmware version 15.27.2

  1. Identify the specific IpTIME router model (T5008, AX2004M, AX3000Q, or AX6000M)
  2. Access the router's admin interface and navigate to the firmware version information section
  3. Download firmware version 15.27.2 or later from the official iptime.com support page
  4. In the router admin interface, go to the firmware upgrade section
  5. Upload the downloaded firmware file (15.27.2 or later) and apply the update
  6. Wait for the upgrade to complete and the router to reboot
  7. Verify the new firmware version is 15.27.2 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in T5008 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24498 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-24498 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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