Cyber Resilience

CVE-2026-16323

Published
21 August 2026
Modified
21 August 2026
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0037 31th percentile
Risk Priority 57 floored blend · peak EPSS

Summary

CVE-2026-16323 is a high-severity EAR (CWE-698) vulnerability in Gov (inferred from references). Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 31th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Execution after redirect (EAR) vulnerability in FuyaWeb Internet and Informatics Services ArchitectPanel Web Admin Panel allows Authentication Bypass. This issue affects ArchitectPanel Web Admin Panel: through 28072026.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-2572Shared CWE-698
CVE-2024-2569Shared CWE-698
CVE-2024-2571Shared CWE-698
CVE-2025-6967Shared CWE-698
CVE-2025-53077Shared CWE-698
CVE-2024-2635Shared CWE-698
CVE-2026-61407Shared CWE-698
CVE-2024-2573Shared CWE-698
CVE-2024-2570Shared CWE-698
CVE-2024-48766Shared CWE-698

Affected Assets

Gov
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover execution paths that continue after a redirect.

Proper access enforcement reduces the impact of continued execution after a redirect by limiting what the remaining code can do.

Requiring a documented secure development process and standards can mandate exiting immediately after issuing redirects.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent improper redirect handling via code review and static analysis, but eliminating only this flaw covers a narrow slice of the control's broader intent.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect EAR flaws before deployment.

prevents

Secure development lifecycle requires proper handling of redirects and exit logic, reducing EAR risk.

prevents

Application security requirements can mandate safe redirect patterns and post-redirect termination.

prevents

Secure architecture principles discourage continued execution after redirects.

prevents

Secure coding standards directly address proper redirect handling and flow termination.

References