# CVE-2026-21822: A path traversal vulnerability has been identified in HCL AppScan 360° (CVE-2026-21822).

> An authenticated attacker can read or write files outside the intended directory in HCL AppScan 360° via path traversal.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-g8rr-pmrr-phx9

## What is CVE-2026-21822?

CVE-2026-21822 is a medium-severity path traversal vulnerability in HCL AppScan 360°, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

HCLSoftware AppScan 360° was affected by a Path Traversal vulnerability in the ASReportService component. Improper handling of file paths allows an authenticated attacker to read or write files outside the intended directory, potentially enabling file system structure inspection or unauthorized file modification within the application's directory scope.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-21822 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-21822 is a medium-severity path traversal vulnerability in HCL AppScan 360°, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-21822 in the wild and no public exploit code.

Affected product: HCL AppScan 360°. 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-21822/ (Markdown: https://insights.sbomify.com/CVE-2026-21822/index.md)
```

## Sources

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

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