Cyber Resilience

CVE-2026-44309

Crypto Weakness

Published
15 May 2026
Modified
17 June 2026
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N
EPSS Score 0.0012 2th percentile
Risk Priority 39 floored blend · peak EPSS

Summary

CVE-2026-44309 is a medium-severity Improper Certificate Validation (CWE-295) vulnerability. Its CVSS base score is 5.3 (Medium).

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

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Gitsign is a keyless Sigstore to signing tool for Git commits with your a GitHub / OIDC identity. Prior to 0.16.0, gitsign verify and gitsign verify-tag re-encode commit/tag objects through go-git's EncodeWithoutSignature before checking the signature, instead of verifying against…

more

the raw git object bytes. For malformed objects with duplicate tree headers, git-core and go-git parse different trees: git-core uses the first, go-git uses the second. A signature crafted over the go-git-normalized form (second tree) passes gitsign verify while git-core resolves the commit to a completely different tree. This breaks the invariant that a verified signature, the commit semantics git-core presents to users, and the object hash logged in Rekor all refer to the same content. This vulnerability is fixed in 0.16.0.

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.
T1557 Adversary-in-the-Middle Credential Access
Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as [Network Sniffing](https://attack.
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-2026-48021Shared CWE-295, CWE-347
CVE-2026-22696Shared CWE-295, CWE-347
CVE-2024-13990Shared CWE-295, CWE-347
CVE-2026-32144Shared CWE-295, CWE-347
CVE-2024-41258Shared CWE-295, CWE-347
CVE-2026-18089Shared CWE-295, CWE-347
CVE-2026-0392Shared CWE-295, 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)
  • 26 hardening rules · 5 OS baselines
Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

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

PKI certificate issuance and acquisition under an approved policy establishes the trusted roots and processes needed for correct validation.

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

Protecting session authenticity depends on cryptographic mechanisms whose trust depends on correct certificate validation.

Requiring confidentiality and integrity protection of transmitted data drives use of properly validated certificates in protocols such as TLS.

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

Certificate-based authentication of users/services/hardware directly depends on correct validation.

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

Proper certificate validation is a core mechanism for protecting data-in-transit confidentiality and integrity.

PR.PS-06 mostly match
prevents

Secure development practices explicitly include implementing correct certificate validation logic.

ID.RA-09 partial match
prevents

Assessing authenticity/integrity of acquired software often relies on code-signing certificate validation.

PR.AA-04 partial match
prevents

Identity assertions conveyed via certificates require validation to be verified.

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.

prevents

Requiring issuance and validation of public-key certificates under an approved policy reduces the chance that certificates with improper validation will be trusted.

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 (3 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-295, CWE-347
  • V-248531 OL 8, for PKI-based authentication, must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor. prevents CWE-295
  • 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-295, 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-295, 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-295, CWE-347
RHEL 8 (2 rules)
  • 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-295, CWE-347
  • 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-295
RHEL 9 (1 rule)
  • V-257822 RHEL 9 must have GPG signature verification enabled for all software repositories. prevents CWE-347

References