Cyber Resilience

CVE-2026-43935

Published
26 May 2026
Modified
24 July 2026
CVSS Score v3.1 8.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
EPSS Score 0.0030 22th percentile
Risk Priority 59 floored blend · peak EPSS

Summary

CVE-2026-43935 is a high-severity Improper Input Validation (CWE-20) vulnerability. Its CVSS base score is 8.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 22th 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 AC-24 (Access Control Decisions) and SA-11 (Developer Testing and Evaluation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A05:2025 InjectionA06:2025 Insecure Design

EU & UK References

Vulnerability Data

e107 is a content management system (CMS). Prior to 2.3.4, a Host Header Injection vulnerability in the password reset page allows attackers to manipulate the Host header to generate password reset links pointing to attacker-controlled domains. This can lead to…

more

phishing attacks, account takeover, or other security risks. The severity is high, as the vulnerability affects a critical function related to user authentication. This vulnerability is fixed in 2.3.4.

CWE(s)
CWE-20CWE-807

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.
attack.mitre.org →
T1036.001 Invalid Code Signature Stealth
Adversaries may attempt to mimic features of valid code signatures to increase the chance of deceiving a user, analyst, or tool.
attack.mitre.org →
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1548 Abuse Elevation Control Mechanism Privilege Escalation
Adversaries may circumvent mechanisms designed to control privilege elevation to gain higher-level permissions.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-7005Shared CWE-20, CWE-807
CVE-2026-42613Shared CWE-20
CVE-2026-42809Shared CWE-20
CVE-2026-3294Shared CWE-20
CVE-2023-31047Shared CWE-20
CVE-2023-3770Shared CWE-20
CVE-2021-21978Shared CWE-20
CVE-2024-21549Shared CWE-20
CVE-2024-25046Shared CWE-20
CVE-2024-52337Shared CWE-20

Affected Assets

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 7 hardening rules · 4 OS baselines
Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

AC-24 Access Control Decisions good match

Explicitly requires that every access decision be based on authoritative, protected decision data rather than caller-supplied inputs.

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover missing input validation through analysis or test cases.

SI-10 Information Input Validation good match

SI-10 directly requires validity checks on information inputs, structurally preventing improper or missing validation.

AC-3 Access Enforcement partial match

Access enforcement requires decisions to be made from trusted policy data rather than modifiable client-supplied inputs.

AC-4 Information Flow Enforcement partial match

Information-flow enforcement applies rules to validated, internal attributes instead of untrusted external values.

SA-15 Development Process, Standards, and Tools partial match

Requiring documented development standards and tools can embed input-validation practices into the engineering process.

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.AA-03 mostly match
prevents

Strong authentication mechanisms directly prevent security decisions from depending on modifiable, untrusted inputs.

PR.AA-04 mostly match
prevents

Verification and protection of identity assertions stops reliance on attacker-controlled values for authorization decisions.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require and enforce input validation during development.

PR.AA-01 partial match
prevents

Proper management of identities/credentials reduces the chance that security decisions will be driven by untrusted inputs.

PR.AA-05 partial match
prevents

Policy-driven, least-privilege authorization reduces opportunities to bypass controls via tampered inputs.

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.

A.8.28 Secure coding mostly match
prevents

Secure coding standards directly prohibit using untrusted inputs for security-critical decisions.

A.8.29 Security testing in development and acceptance mostly match
finds

Testing against a defined set of requirements and using code review plus vulnerability scanning forces validation of inputs and handling of unanticipated conditions, reducing the chance that malformed data will be accepted.

A.8.16 Monitoring activities partial match
finds

Monitoring can detect exploitation but does not stop the underlying weakness.

A.8.25 Secure development life cycle partial match
prevents

Secure-coding guidelines and mandatory security testing (including code scans) compel developers to validate and sanitize inputs at design and implementation time, lowering the incidence of malformed or malicious data reaching downstream components.

A.8.26 Application security requirements partial match
prevents

Mandating input controls that include integrity checks and input validation ensures that untrusted data is examined before use, blocking the root cause of many injection and malformed-data weaknesses.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Security-by-design principles explicitly call for data validation and sanitization at every layer, reducing the chance that malformed or malicious input will be processed without scrutiny.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

RHEL 8 (1 rule)
  • V-230265 RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-20

References