# CVE-2026-21811: Multiple security vulnerabilities affect HCL AppScan Azure Boards Plugin (CVE-2026-12143 and CVE-2026-13149)


- **Severity:** Low 3.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** GHSA-c8p7-j7hh-mm95

## What is CVE-2026-21811?

CVE-2026-21811 is a low-severity vulnerability in HCL Software AppScan Integration with Azure Boards for ASoC & A360, published on 22 Oct 2026. 

### Official description

HCL AppScan Azure Boards Plugin is potentially affected by an Information Disclosure vulnerability involving secrets accessible in plaintext during pipeline execution. Depending on the pipeline configuration, these secrets could be exposed through task outputs, debug logs, environment variable dumps, or build agent scripts, despite being masked in the user interface.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


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

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

## Is CVE-2026-21811 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-21811 is a low-severity vulnerability in HCL Software AppScan Integration with Azure Boards for ASoC & A360, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-21811 in the wild and no public exploit code.

Affected product: HCL Software AppScan Integration with Azure Boards for ASoC & A360. 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-21811/ (Markdown: https://insights.sbomify.com/CVE-2026-21811/index.md)
```

## Sources

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

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