LiveActive security incident?Get immediate response
CVE Record

CVE-2022-26461: In vow, there is a possible undefined behavior due to an API misuse.

In vow, there is a possible undefined behavior due to an API misuse. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07032604; Issue ID: ALPS07032604.

MediumCVSS 6.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This MediaTek flaw affects certain Android 11 and 12 devices using listed MediaTek chipsets. It can let a local attacker who already has high privileges escalate further to System-level impact. It is not described as remote, unauthenticated, or actively exploited in the provided sources.

Executive priority

Treat as a moderate mobile fleet risk. It is not presented as remotely exploitable, but System-level impact makes it important for devices used by executives, administrators, field staff, or regulated-data workflows.

Technical view

CVE-2022-26461 is an API misuse in MediaTek's vow component causing possible undefined behavior. CVSS 3.1 is 6.7 with local attack vector, low complexity, high privileges required, no user interaction, and high confidentiality, integrity, and availability impact. MediaTek tracks the fix as ALPS07032604.

Likely exposure

Exposure is most likely on Android 11 or 12 devices using the named MediaTek platforms, including MT6833 through MT6983 and MT8791/MT8797, before OEM firmware includes MediaTek patch ALPS07032604.

Exploitation context

The provided sources do not show active exploitation or public exploit details. The CVSS vector requires local access and high existing privileges, so practical risk is higher when combined with another compromise, malicious privileged app, or weak device management.

Researcher notes

Evidence is sparse: the public record names vow, API misuse, undefined behavior, and patch ID ALPS07032604, but does not describe root cause, reachable interfaces, exploit chains, or affected device models beyond chipset and Android version lists.

Mitigation direction

  • Apply OEM firmware or Android security updates containing MediaTek patch ALPS07032604.
  • Prioritize managed devices handling sensitive business data or privileged mobile workflows.
  • Restrict installation and granting of privileged permissions to untrusted Android apps.
  • Check MediaTek and device OEM advisories for model-specific fixed builds.

Validation and detection

  • Inventory Android devices for affected MediaTek chipsets and Android 11 or 12.
  • Verify each device security patch level and OEM firmware release notes.
  • Confirm remediation references ALPS07032604 or MediaTek September 2022 fixes.
  • Flag unsupported or unpatched affected devices for replacement or isolation.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-670: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-26461 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.7 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.7CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H0.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.7Medium
CVSS 3.1 vector shape for CVE-2022-26461Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MediaTek, Inc.MT6833, MT6853, MT6855, MT6873, MT6877, MT6879, MT6883, MT6885, MT6889, MT6893, MT6895, MT6983, MT8791, MT8797Android 11.0, 12.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-670 · source CWE mapping

Always-Incorrect Control Flow Implementation

Always-Incorrect Control Flow Implementation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.