# CVE-2026-102363: mall4j through 4.0 Unauthenticated Shipment Tracking Disclosure via Order Number

> Unauthenticated attackers can access sensitive shipment tracking details for any order by supplying an order number, exposing logistics data.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-6rjg-gfrv-7842

## What is CVE-2026-102363?

CVE-2026-102363 is a medium-severity missing authorization vulnerability in gz-yami mall4j, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

mall4j through 4.0 contains a missing authentication vulnerability in the DeliveryController checkDelivery endpoint that allows unauthenticated attackers to read shipment tracking information by supplying an order number parameter. Attackers can access carrier names, waybill numbers, and complete logistics trails for any order without authentication or ownership verification.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-102363 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102363 is a medium-severity missing authorization vulnerability in gz-yami mall4j, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-102363 exists.

Affected product: gz-yami mall4j. 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-102363/ (Markdown: https://insights.sbomify.com/CVE-2026-102363/index.md)
```

## Sources

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

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