# CVE-2026-5452: UCC CampusConnect App campusconnect.ucc BuildConfig.java hard-coded key

> A hard-coded cryptographic key in the UCC CampusConnect Android app allows local attackers to bypass security controls.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **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:** 3 Apr 2026
- **Updated:** 3 Apr 2026
- **Also known as:** GHSA-mqg3-gfr2-qw8p

## What is CVE-2026-5452?

CVE-2026-5452 is a medium-severity vulnerability in UCC CampusConnect App, published on 3 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw has been found in UCC CampusConnect App up to 14.3.5 on Android. This vulnerability affects unknown code of the file campusconnect/BuildConfig.java of the component campusconnect.ucc. This manipulation causes use of hard-coded cryptographic key
 . The attack can only be executed locally. The exploit has been published and may be used.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key), CWE-320

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


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

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

## Is CVE-2026-5452 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5452 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5452 is a medium-severity vulnerability in UCC CampusConnect App, published on 3 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5452 exists.

Affected product: UCC CampusConnect App. 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-5452/ (Markdown: https://insights.sbomify.com/CVE-2026-5452/index.md)
```

## Sources

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

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