# CVE-2026-0634: Code Execution in AssistFeedbackService on TECNO Pova7 Pro 5G

> Local apps can execute arbitrary code as system via command injection in AssistFeedbackService on TECNO Pova7 Pro 5G.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2026
- **Updated:** 2 Apr 2026
- **Also known as:** GHSA-pq33-qwwq-ggx5

## What is CVE-2026-0634?

CVE-2026-0634 is a high-severity command injection vulnerability in TECNO Pova7 Pro 5G, published on 2 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Code execution in AssistFeedbackService of TECNO Pova7 Pro 5G on Android allows local apps to execute arbitrary code as system via command injection.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

## Which versions are affected by CVE-2026-0634?


## How do I fix CVE-2026-0634?

No fix has been published for CVE-2026-0634 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-0634 being exploited?

There is no known exploitation of CVE-2026-0634 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-0634 and fix it if it is affected.

What it is: CVE-2026-0634 is a high-severity command injection vulnerability in TECNO Pova7 Pro 5G, published on 2 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-0634 in the wild and no public exploit code.

Affected product: TECNO Pova7 Pro 5G. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-0634/ (Markdown: https://insights.sbomify.com/CVE-2026-0634/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-0634
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-0634
- OSV: https://osv.dev/vulnerability/CVE-2026-0634

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-0634/
Summaries are generated and may contain mistakes; the official description above is the record.