On this page
CWE-321: Use of Hard-coded Cryptographic Key
Weakness Summary
The product uses a hard-coded, unchangeable cryptographic key.
- Canonical source: MITRE CWE-321 (opens in a new tab)
- Published Atomicorp CVE observations: 1
- Distinct affected products in those observations: 1
- Active Atomicorp rules associated with this weakness: 9
Atomicorp Research Context
Atomicorp has published CVE-specific research observations associated with this weakness category. Each linked CVE page states whether the tested request was detected or blocked and is the authoritative customer-facing finding.
The CVEs and rules shown here are selected published examples, not a complete list of Atomicorp protections. If a CWE, CVE, or rule is absent from this page, no conclusion should be drawn about whether Atomicorp protects against that weakness or attack method.
A CWE describes a class of software weakness. It does not identify one exploit request, and association with a CWE does not mean that every vulnerability or exploitation path in that category is detected or blocked.
Selected Published CVE Observations
| CVE | Vulnerability | Product | Atomicorp finding | Observed rules |
|---|---|---|---|---|
| CVE-2026-89026 | Issabel Framework Hard-coded JWT Key RCE via pbxapi/manager/originate | Issabel Framework | Protected by Atomicorp rules | 340014 , 340023 , 340029 , 344360 , 344361 , 344363 , 344364 , 344366 , 344370 |
Associated Atomicorp WAF Rules
| Rule | Status | Behavior |
|---|---|---|
| 340014 | Active | disruptive (deny) |
| 340023 | Active | disruptive (deny) |
| 340029 | Active | disruptive (deny) |
| 344360 | Active | disruptive (deny) |
| 344361 | Active | disruptive (deny) |
| 344363 | Active | disruptive (deny) |
| 344364 | Active | disruptive (deny) |
| 344366 | Active | disruptive (deny) |
| 344370 | Active | disruptive (deny) |