Categories
CVE-2026-56758 medium CVSS 6.5

Out-of-Bounds Read in AARQ PDUs during MMS connection establishment (CVE-2026-56758)

Summary

Vulnerability in AARQ PDUs during MMS connection establishment (CVE-2026-56758). Risk of unauthorized operations or information disclosure.

Original description

The description as published by the source.

The ACSE layer contains a flaw in the processing of AARQ PDUs during MMS
connection establishment. When parsing certain fields within the
calling AP title, an attacker controlled length value of zero or one may
cause the parser to read past the end of a heap buffer.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-56758 has been found in AARQ PDUs during MMS connection establishment.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "AARQ PDUs during MMS connection establishment CVE-2026-56758" on the vendor's site.

CVE-2026-56758 (AARQ PDUs during MMS connection establishment) — CWE-125 / CVSS v3 6.5
Attack vector: adjacent-network / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Out-of-bounds read (CWE-125) exists in AARQ PDUs during MMS connection establishment.

📍 Affected scope

Check the vendor advisory for the affected versions of AARQ PDUs during MMS connection establishment.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで AARQ PDUs during MMS connection establishment を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details