Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 0.35% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-26007High confidence
cryptography Subgroup Attack Due to Missing Subgroup Validation for SECT Curves
pyca · cryptography
Official source article: GitHub GHSA-R6PH-V2QM-Q3C2 ↗. Check the applicable product and release in the original source.
8.2HighCVSS 4.0
Patch only the product branches with a verified fix
Fix availability varies by productHigh technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs pyca cryptography and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Debian Security Tracker: 1 affected package state with no published fix
Distribution package intelligence
6 package statesRelease-specific package status
Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Package result overrides the generic status
BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Alpine v3.23v3.23 · main | py3-cryptography | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 46.0.5-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Debian trixietrixie · source | python-cryptography | Vendor fix publishedDebian records a fixed source-package version for this release. | 43.0.0-3+deb13u1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | python-cryptography | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | python-cryptography | Vendor fix publishedDebian records a fixed source-package version for this release. | 46.0.5-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | python-cryptography | Vendor fix publishedDebian records a fixed source-package version for this release. | 46.0.5-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | python-cryptography | Vendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree. | 41.0.7-4ubuntu0.3 | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
Open-source package ranges2 source-attributed ranges
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| PyPIcryptography | ECOSYSTEM: introduced 0; fixed 46.0.5 | 46.0.5 | OSV record ↗aggregator derived · 10 Sep 2026 |
| pipcryptography | <= 46.0.4 | 46.0.5 | GitHub advisory ↗upstream repository advisory · 13 Feb 2026 |
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2026-26007 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitycryptography: cryptography Subgroup Attack Due to Missing Subgroup Validation for SECT Curves
The vendor explicitly identifies these products as affected by this CVE.
- openshift-lightspeed/lightspeed-ocp-rag-rhel9 as a component of OpenShift Lightspeed
- openshift-lightspeed/lightspeed-service-api-rhel9 as a component of OpenShift Lightspeed
- ansible-automation-platform-26/controller-rhel9 as a component of Red Hat Ansible Automation Platform 2
- ansible-automation-platform-26/gateway-rhel9 as a component of Red Hat Ansible Automation Platform 2
- ansible-automation-platform-tech-preview/automation-dashboard-rhel9 as a component of Red Hat Ansible Automation Platform 2
- ansible-automation-platform/automation-dashboard-rhel9 as a component of Red Hat Ansible Automation Platform 2
- rhoai/odh-llama-stack-core-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
- rhoai/odh-trustyai-ragas-lls-provider-dsp-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
- python3.12-cryptography.src as a component of Red Hat Satellite 6
- satellite/iop-advisor-engine-rhel9 as a component of Red Hat Satellite 6
- satellite/iop-host-inventory-rhel9 as a component of Red Hat Satellite 6
- satellite/iop-insights-engine-rhel9 as a component of Red Hat Satellite 6
- Summary
- A validation flaw has been discovered in the python cryptography package. This missing validation allows an attacker to provide a public key point P from a small-order subgroup. This can lead to security issues in various situations, such as the most commonly used signature verification (ECDSA) and shared key negotiation (ECDH). When the victim computes the shared secret as S = [victim_private_key]P via ECDH, this leaks information about victim_private_key mod (small_subgroup_order). For curves with cofactor > 1, this reveals the least significant bits of the private key. When these weak public keys are used in ECDSA , it's easy to forge signatures on the small subgroup. Only SECT curves are impacted by this.
- Remediation
- For details on how to apply this update, refer to Ansible Automation Platform documentation.
High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. Prior to 46.0.5, the public_key_from_numbers (or EllipticCurvePublicNumbers.public_key()), EllipticCurvePublicNumbers.public_key(), load_der_public_key() and load_pem_public_key() functions do not verify that the point belongs to the expected prime-order subgroup of the curve. This missing validation allows an attacker to provide a public key point P from a small-order subgroup. This can lead to security issues in various situations, such as the most commonly used signature verification (ECDSA) and shared key negotiation (ECDH). When the victim computes the shared secret as S = [victim_private_key]P via ECDH, this leaks information about victim_private_key mod (small_subgroup_order). For curves with cofactor > 1, this reveals the least significant bits of the private key. When these weak public keys are used in ECDSA , it's easy to forge signatures on the small subgroup. Only SECT curves are impacted by this. This vulnerability is fixed in 46.0.5.
What
cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. Prior to 46.0.5, the public_key_from_numbers (or EllipticCurvePublicNumbers.public_key()), EllipticCurvePublicNumbers.public_key(), load_der_public_key() and load_pem_public_key() functions do not verify that the point belongs to the expected prime-order subgroup of the curve. This missing validation allows an attacker to provide a public key point P from a small-order subgroup. This can lead to security issues in various situations, such as the most commonly used signature verification (ECDSA) and shared key negotiation (ECDH). When the victim computes the shared secret as S = [victim_private_key]P via ECDH, this leaks information about victim_private_key mod (small_subgroup_order). For curves with cofactor > 1, this reveals the least significant bits of the private key. When these weak public keys are used in ECDSA , it's easy to forge signatures on the small subgroup. Only SECT curves are impacted by this. This vulnerability is fixed in 46.0.5.
Why
The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. Prior to 46.0.5, the public_key_from_numbers (or EllipticCurvePublicNumbers.public_key()), EllipticCurvePublicNumbers.public_key(), load_der_public_key() and load_pem_public_key() functions do not verify that the point belongs to the expected prime-order subgroup of the curve. This missing validation allows an attacker to provide a public key point P from a small-order subgroup. This can lead to security issues in various situations, such as the most commonly used signature verification (ECDSA) and shared key negotiation (ECDH). When the victim computes the shared secret as S = [victim_private_key]P via ECDH, this leaks information about victim_private_key mod (small_subgroup_order). For curves with cofactor > 1, this reveals the least significant bits of the private key. When these weak public keys are used in ECDSA , it's easy to forge signatures on the small subgroup. Only SECT curves are impacted by this. This vulnerability is fixed in 46.0.5.
Why
The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Insufficient Verification of Data Authenticity → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- High: exploitation depends on specific conditions
- Security boundary
- Not a CVSS 4.0 base metric
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-345 ↗
CWE-345: Insufficient Verification of Data Authenticity. The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NCommon Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.ATNoneAttack requirements: No additional deployment or execution condition is required.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCHighVulnerable-system confidentiality: A successful attack can cause a major loss.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VANoneVulnerable-system availability: No direct loss is represented by this metric.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Affected
- openshift-lightspeed/lightspeed-ocp-rag-rhel9 as a component of OpenShift Lightspeed
- openshift-lightspeed/lightspeed-service-api-rhel9 as a component of OpenShift Lightspeed
- ansible-automation-platform-26/controller-rhel9 as a component of Red Hat Ansible Automation Platform 2
- ansible-automation-platform-26/gateway-rhel9 as a component of Red Hat Ansible Automation Platform 2
- ansible-automation-platform-tech-preview/automation-dashboard-rhel9 as a component of Red Hat Ansible Automation Platform 2
- ansible-automation-platform/automation-dashboard-rhel9 as a component of Red Hat Ansible Automation Platform 2
- rhoai/odh-llama-stack-core-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
- rhoai/odh-trustyai-ragas-lls-provider-dsp-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
- python3.12-cryptography.src as a component of Red Hat Satellite 6
- satellite/iop-advisor-engine-rhel9 as a component of Red Hat Satellite 6
- satellite/iop-host-inventory-rhel9 as a component of Red Hat Satellite 6
- satellite/iop-insights-engine-rhel9 as a component of Red Hat Satellite 6
- satellite/iop-vmaas-rhel9 as a component of Red Hat Satellite 6
- rhtas/model-transparency-rhel9 as a component of Red Hat Trusted Artifact Signer
- Fixed
- automation-controller-venv-tower-0:4.6.28-3.el8ap.aarch64 as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 8
- automation-controller-venv-tower-0:4.6.28-3.el8ap.ppc64le as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 8
- automation-controller-venv-tower-0:4.6.28-3.el8ap.s390x as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 8
- automation-controller-venv-tower-0:4.6.28-3.el8ap.x86_64 as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 8
- automation-controller-venv-tower-0:4.6.28-3.el9ap.aarch64 as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 9
- automation-controller-venv-tower-0:4.6.28-3.el9ap.ppc64le as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 9
- automation-controller-venv-tower-0:4.6.28-3.el9ap.s390x as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 9
- automation-controller-venv-tower-0:4.6.28-3.el9ap.x86_64 as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 9
- fence-agents-0:4.2.1-129.el8_10.25.src as a component of Red Hat Enterprise Linux AppStream (v. 8)
- fence-agents-aliyun-debuginfo-0:4.2.1-129.el8_10.25.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)
- fence-agents-all-0:4.2.1-129.el8_10.25.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)
- fence-agents-all-0:4.2.1-129.el8_10.25.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)
- fence-agents-all-0:4.2.1-129.el8_10.25.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)
- fence-agents-all-0:4.2.1-129.el8_10.25.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)
- fence-agents-amt-ws-0:4.2.1-129.el8_10.25.noarch as a component of Red Hat Enterprise Linux AppStream (v. 8)
- fence-agents-apc-0:4.2.1-129.el8_10.25.noarch as a component of Red Hat Enterprise Linux AppStream (v. 8)
- fence-agents-apc-snmp-0:4.2.1-129.el8_10.25.noarch as a component of Red Hat Enterprise Linux AppStream (v. 8)
- fence-agents-azure-arm-debuginfo-0:4.2.1-129.el8_10.25.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)
- fence-agents-bladecenter-0:4.2.1-129.el8_10.25.noarch as a component of Red Hat Enterprise Linux AppStream (v. 8)
- fence-agents-brocade-0:4.2.1-129.el8_10.25.noarch as a component of Red Hat Enterprise Linux AppStream (v. 8)
- fence-agents-cisco-mds-0:4.2.1-129.el8_10.25.noarch as a component of Red Hat Enterprise Linux AppStream (v. 8)
- fence-agents-cisco-ucs-0:4.2.1-129.el8_10.25.noarch as a component of Red Hat Enterprise Linux AppStream (v. 8)
- fence-agents-common-0:4.2.1-129.el8_10.25.noarch as a component of Red Hat Enterprise Linux AppStream (v. 8)
- fence-agents-compute-0:4.2.1-129.el8_10.25.noarch as a component of Red Hat Enterprise Linux AppStream (v. 8)
- fence-agents-debuginfo-0:4.2.1-129.el8_10.25.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)
- fence-agents-debuginfo-0:4.2.1-129.el8_10.25.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)
- fence-agents-debuginfo-0:4.2.1-129.el8_10.25.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)
- fence-agents-debuginfo-0:4.2.1-129.el8_10.25.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)
- fence-agents-debugsource-0:4.2.1-129.el8_10.25.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)
- fence-agents-debugsource-0:4.2.1-129.el8_10.25.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)
- and 855 more
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 10 Feb 2026 · Last source change 16 Sept 2026, 12:04 UTC · CWE-345 · Insufficient Verification of Data Authenticity
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-6238
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- < 46.0.5 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- After
- cryptography: < 46.0.5 · Fixed: RHSA-2026:13512: Red Hat Ansible Automation Platform 2.5 for RHEL 8, Red Hat Ansible Automation Platform 2.5 for RHEL 9
CVE published
Fixed release or patch reference recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.