dbcve.org
Indoor Connect 8855 FirmwareOperating system · Ericsson

CVE-2025-27260

HIGH · 7.5 CVSS v3.1 Published 2026-03-25
Fix available
A fix is available. Upgrade to 2025.q3 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
Ericsson Indoor Connect 8855 versions prior to 2025.Q3 contains an Improper Filtering of Special Elements vulnerability which, if exploited, can lead to unauthorized modification of certain information

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

Ericsson Indoor Connect 8855 devices prior to firmware 2025.Q3 contain an Improper Filtering of Special Elements vulnerability. This input validation flaw allows attackers to inject special elements (likely characters or commands) that are not properly sanitized, potentially enabling unauthorized modification of system data or configuration settings.

MitigationApply the vendor firmware update (2025.Q3 or later) when available. Until then, restrict network access to the device management interface to trusted sources only.

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.q3

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Confirm device model is Ericsson Indoor Connect 8855
    Access the device web interface or CLI and verify the model number displays as 'Indoor Connect 8855' in the system information or device status page
    Affected if The device model is Ericsson Indoor Connect 8855 and is reachable on the network
  2. Check installed firmware version
    Navigate to the device management interface firmware or system settings page and locate the firmware version number; compare it against the affected range of versions prior to 2025.Q3
    Affected if The installed firmware version is any build earlier than 2025.Q3 (e.g., 2025.Q2, 2025.Q1, 2024.x, etc.)
  3. Identify management interface exposure
    Check the device network configuration for HTTP/HTTPS management access and determine if the interface is bound to WAN/outside-facing IP addresses or is accessible from untrusted networks
    Affected if The device management interface is accessible from external/untrusted networks rather than only from isolated management VLANs or trusted internal subnets
  4. Review for configuration modification indicators
    Examine system logs, audit logs, or configuration change history for any unauthorized or unexpected modifications to device settings, particularly in input fields that accept user-provided data
    Affected if Unexpected configuration changes exist that were not initiated by legitimate administrators, or suspicious input patterns appear in logs

You are affected if you have an Ericsson Indoor Connect 8855 device running firmware versions earlier than 2025.Q3 with its management interface accessible to untrusted networks.

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

Apply the vendor firmware update (2025.Q3 or later) when available. Until then, restrict network access to the device management interface to trusted sources only.

Recommended fix Moderate confidence

2025.Q3

  1. 1. Identify the current firmware version of the Ericsson Indoor Connect 8855 device
  2. 2. Download the firmware version 2025.Q3 from Ericsson's official support portal or authorized distribution channels
  3. 3. Review the firmware release notes for any specific upgrade prerequisites or procedures
  4. 4. Create a backup of the current device configuration before proceeding with the upgrade
  5. 5. Follow the standard Ericsson firmware upgrade procedure for the Indoor Connect 8855 (typically via web interface, CLI, or management software)
  6. 6. Verify the upgrade was successful by confirming the device reports firmware version 2025.Q3
  7. 7. Restore the configuration backup if needed and verify normal operation

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
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27260 — 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-2025-27260 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