Indoor Connect 8855 FirmwareOperating system · Ericsson

CVE-2025-27262

HIGH · 7.8 CVSS v3.1 Published 2025-09-25
Fix available
A fix is available. Upgrade to 2025.q2 or later.
See remediation →
80/100
Remediation priority · High
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
Ericsson Indoor Connect 8855 contains a command injection vulnerability which if exploited can result in an escalation of privileges.

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

Command injection vulnerability in Ericsson Indoor Connect 8855 allows an attacker to inject arbitrary commands through insufficient input validation, leading to privilege escalation from the application context to root/system level.

MitigationApply vendor-provided firmware patch when available; restrict management interface access to trusted networks and enforce strong authentication to reduce attack surface.

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
Indoor Connect 8855 FirmwareOperating system
Affected:< 2025.q2

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Confirm device model
    Identify the Ericsson Indoor Connect 8855 device in your inventory or network. Check device labeling, management interface, or SNMP/Bonjour discovery for the exact model number.
    Affected if Device is not an Ericsson Indoor Connect 8855 unit.
  2. Determine installed firmware version
    Access the device management interface (web UI, CLI, or SNMP) and locate the firmware version information. Compare against the 2025.q2 release.
    Affected if Firmware version is earlier than 2025.q2 (e.g., 2024.x, 2023.x, or any version without the Q2 2025 patch).
  3. Verify management interface accessibility
    Check network exposure of the device management interface (HTTP/HTTPS, SSH, or telnet). Determine if it is reachable from untrusted networks.
    Affected if Management interface is exposed to untrusted networks without network segmentation.
  4. Assess input handling exposure
    If you have access to the device, review which user-facing features accept input (web forms, API endpoints, CLI parameters). The vulnerability allows command injection through insufficient input validation.
    Affected if Any management or configuration feature accepts user-supplied input without sanitization.

You are affected if you are running an Ericsson Indoor Connect 8855 device with firmware version earlier than 2025.q2, and the management interface or any input-handling feature is accessible to potential attackers.

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 2025.q2 or later
Fixed in 2025.q2
Interim mitigation

Apply vendor-provided firmware patch when available; restrict management interface access to trusted networks and enforce strong authentication to reduce attack surface.

Recommended fix Moderate confidence

2025.q2 (or later firmware release)

  1. Identify the current firmware version of the Ericsson Indoor Connect 8855 device
  2. Download the firmware version 2025.q2 or later from the official Ericsson support portal
  3. Review the firmware release notes for any specific update instructions
  4. Apply the firmware update following Ericsson's official documentation for the Indoor Connect 8855
  5. After updating, verify the device is functioning correctly and the firmware version shows 2025.q2 or later
Caveat Review Ericsson release notes for 2025.q2 to check for any configuration or feature changes that may affect your deployment

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

Fix this in Indoor Connect 8855 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2025-27262 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