Cyber Resilience

CVE-2026-42462

Published
10 June 2026
Modified
17 June 2026
CVSS Score v3.1 7.0
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:L
EPSS Score 0.0017 7th percentile
Risk Priority 51 floored blend · peak EPSS

Summary

CVE-2026-42462 is a high-severity Incorrect Behavior Order: Validate Before Canonicalize (CWE-180) vulnerability. Its CVSS base score is 7.0 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Supply Chain Compromise (T1195); ranked at the 7th 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 SC-13 (Cryptographic Protection) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Fedify is a TypeScript library for building federated server apps powered by ActivityPub. Prior to versions 1.9.11, 1.10.10, 2.0.18, 2.1.14, and 2.2.3, an attacker can make use of JSON-LD features to restructure a JSON-LD document that would change how Fedify…

more

interprets it without changing its Linked Data Signature, allowing them to alter a third-party signed activity they have received. Versions 1.9.11, 1.10.10, 2.0.18, 2.1.14, and 2.2.3 fix the issue.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1195 Supply Chain Compromise Initial Access
Adversaries may manipulate products or product delivery mechanisms prior to receipt by a final consumer for the purpose of data or system compromise.
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.
T1195.002 Compromise Software Supply Chain Initial Access
Adversaries may manipulate application software prior to receipt by a final consumer for the purpose of data or system compromise.
T1542 Pre-OS Boot Stealth
Adversaries may abuse Pre-OS Boot mechanisms as a way to establish persistence on a system.
T1553 Subvert Trust Controls Defense Impairment
Adversaries may undermine security controls that will either warn users of untrusted activity or prevent execution of untrusted programs.
T1553.002 Code Signing Defense Impairment
Adversaries may create, acquire, or steal code signing materials to sign their malware or tools.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-25292Shared CWE-347, CWE-436
CVE-2025-25291Shared CWE-347, CWE-436
CVE-2025-3757Shared CWE-347
CVE-2023-3347Shared CWE-347
CVE-2025-4658Shared CWE-347
CVE-2024-41254Shared CWE-347
CVE-2026-15265Shared CWE-347
CVE-2026-5050Shared CWE-347
CVE-2026-48558Shared CWE-347
CVE-2026-23967Shared CWE-347

Affected Assets

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 14 hardening rules · 5 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V5.2.2
  • V9.1.3
  • V10.4.6
  • V1.3.8

Mitigating Controls (NIST 800-53 r5) AI

SA-11 requires developer testing and evaluation that can discover validation-order defects after they have been coded.

Requiring cryptographic protection mechanisms forces correct signature verification to be implemented for data protection.

SI-10 requires validity checks on inputs; when implemented with canonicalization preceding validation it structurally prevents the exact ordering flaw.

Mandating integrity verification tools directly requires proper cryptographic signature checking to detect unauthorized changes.

SA-8 mandates security engineering principles that include correct canonicalization-before-validation ordering for input handling.

Protecting session authenticity requires correct verification of cryptographic signatures or equivalent mechanisms.

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.DS-01 mostly match
prevents

Digital signatures are explicitly cited to protect integrity of data-at-rest, so proper verification directly mitigates the weakness.

PR.DS-02 mostly match
prevents

Digital signatures are explicitly cited to protect integrity of data-in-transit, so proper verification directly mitigates the weakness.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require correct validation order after canonicalization to prevent bypasses.

DE.AE-03 partial match
prevents

Correlating logs from multiple products can surface discrepancies caused by interpretation conflicts.

DE.CM-09 partial match
prevents

Runtime monitoring of software behavior can detect adverse outcomes stemming from differing interpretations.

GV.SC-07 partial match
prevents

Supplier risk assessments can identify products whose differing interpretations create systemic exposure.

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 validation-order defects before deployment.

prevents

Establishing approved cryptographic solutions and usage practices lowers the probability that signature-verification steps will be omitted or incorrectly implemented.

prevents

Secure SDLC mandates input validation and canonicalization order, directly addressing CWE-180.

prevents

Application security requirements include proper input handling to prevent validation-before-canonicalization flaws.

prevents

Secure architecture principles reduce the likelihood of ordering errors in input processing.

prevents

Secure coding standards explicitly require canonicalize-then-validate to eliminate CWE-180.

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).

Oracle Linux 8 (2 rules)
  • V-248574 YUM must be configured to prevent the installation of patches, service packs, device drivers, or OL 8 system components that have not been digitally signed using a certificate that is recognized and approved by the organization. prevents CWE-347
  • V-248575 OL 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-347
Oracle Linux 9 (2 rules)
  • V-271525 OL 9 must have GPG signature verification enabled for all software repositories. prevents CWE-347
  • V-271523 OL 9 must check the GPG signature of locally installed software packages before installation. prevents CWE-347
RHEL 7 (2 rules)
  • V-204447 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository 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-347
  • V-204448 The Red Hat Enterprise Linux operating system 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-347
RHEL 8 (1 rule)
  • V-230264 RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository 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-347
RHEL 9 (1 rule)
  • V-257822 RHEL 9 must have GPG signature verification enabled for all software repositories. prevents CWE-347

References