Ella Core Has Audit Log Falsification via Path/Body IMSI Mismatch in UpdateSubscriber

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2026-34762: 0.19% estimated exploitation activity in the next 30 days; percentile 8.92 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The PUT /api/v1/subscriber/{imsi} API accepts an IMSI identifier from both the URL path and the JSON request body but never verifies they match. This allows an authenticated NetworkManager to modify any subscriber's policy while the audit trail records a fabricated or unrelated subscriber IMSI. Impact A NetworkManager or Admin can modify any subscriber's QoS policy (potentially degrading service or altering traffic routing) while the audit log attributes the change to a non-existent or unrelated subscriber. Post-incident forensic searches for the affected subscriber's IMSI would find no matching audit entries. Fix Remove the IMSI as a body param and use the path param as a single source of truth.

Published by the source

1 Apr 2026, 22:59 UTC

Last modified by the source

6 Apr 2026, 17:32 UTC

Source last checked

26 Oct 2026, 15:19 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-xw45-cc32-442f

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-34762

Advisory: Ella Core Has Audit Log Falsification via Path/Body IMSI Mismatch in UpdateSubscriber
IDs: CVE-2026-34762, GHSA-xw45-cc32-442f
Record: https://patchnext.com/advisories/cve-2026-34762 (revision 1, source checked 26 Oct 2026, 15:19 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/ellanetworks/core 1.8.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/ellanetworks/core: affected <= 1.7.0; fixed in 1.8.0

## Suggested inspection (read-only)
- Go github.com/ellanetworks/core: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/ellanetworks/core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-xw45-cc32-442f (GitHub-reviewed advisory GHSA-xw45-cc32-442f lists affected ranges: Go github.com/ellanetworks/core >=0 <=1.7.0)

Commands are suggestions: review each one before running it.