Cyber Resilience

CVE-2026-11348

Published
07 July 2026
Modified
07 July 2026
CVSS Score v3.1 8.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0019 8th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2026-11348 is a high-severity Improper Verification of Cryptographic Signature (CWE-347) vulnerability in Gov (inferred from references). Its CVSS base score is 8.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Code Signing (T1553.002); ranked at the 8th 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 SI-7 (Software, Firmware, and Information Integrity) and CM-14 (Signed Components) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A04:2025 Cryptographic Failures

EU & UK References

Vulnerability Data

Improper verification of cryptographic signature vulnerability in HAVELSAN Inc. Liman MYS allows Fake the Source of Data. This issue affects Liman MYS: before release.Master.1107.

CWE(s)
CWE-347

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1553.002 Code Signing Defense Impairment
Adversaries may create, acquire, or steal code signing materials to sign their malware or tools.
attack.mitre.org →
Why these techniques?

CWE-347 directly enables bypassing code signature verification to masquerade malicious data/code as legitimate.

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-48758Shared CWE-347
CVE-2026-3338Shared CWE-347
CVE-2026-49834Shared CWE-347
CVE-2026-40941Shared CWE-347
CVE-2026-0234Shared CWE-347
CVE-2026-52754Shared CWE-347
CVE-2026-6331Shared CWE-347
CVE-2026-9779Shared CWE-347
CVE-2025-64787Shared CWE-347
CVE-2025-67903Shared CWE-347

Affected Assets

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

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-7 Software, Firmware, and Information Integrity
  • SC-8 Transmission Confidentiality and Integrity
  • CM-14 Signed Components
Detect
Catch it (NIST detect / respond)

—

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

—

Mitigating Controls (NIST 800-53 r5) AI

SI-7 Software, Firmware, and Information Integrity good match
prevent

Directly requires cryptographic integrity verification mechanisms to detect unauthorized or unsigned data, preventing the exact signature bypass described by CWE-347.

SC-8 Transmission Confidentiality and Integrity partial match
prevent

Mandates cryptographic protections that ensure data origin authenticity and integrity during transmission, mitigating spoofed data sources when properly implemented.

CM-14 Signed Components partial match
prevent

Requires that only signed components from approved authorities are accepted, enforcing the signature verification step missing in the vulnerable Liman MYS release.

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.

ID.RA-09 partial match
prevents

Requires assessing authenticity and integrity of acquired assets, which commonly relies on signature verification but is limited to pre-acquisition.

PR.PS-06 partial match
prevents

Secure SDLC practices include code signing and signature verification requirements, addressing the weakness during development.

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.24 Use of cryptography partial match
prevents

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

Hardening callouts derived

Configuration rules from DISA STIG baselines that reduce the attack surface for weaknesses of the type cited by this CVE. Derived transitively via CVE→CWE→STIG over `controls_xwalks` (authoritative rows only).

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. via 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. via CWE-347
Oracle Linux 9 (2 rules)
  • V-271523 OL 9 must check the GPG signature of locally installed software packages before installation. via CWE-347
  • V-271525 OL 9 must have GPG signature verification enabled for all software repositories. via 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. via CWE-347
RHEL 9 (1 rule)
  • V-257822 RHEL 9 must have GPG signature verification enabled for all software repositories. via CWE-347

References