Cipher.update_into can corrupt memory in pyca cryptography
cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. In affected versions `Cipher.update_into` would accept Python objects which implement the buffer protocol, but provide only immutable buffers. This would allow immutable objects (such as `bytes`) to be mutated, thus violating fundamental rules of Python and resulting in corrupted output. This now correctly raises an exception. This issue has been present since `update_into` was originally introduced in cryptography 1.8.
- BDU:2023-02656
- GHSA-w7pp-m8wf-vj6r
- ALSA-2023:6615
- ALSA-2023:7096
- ALSA-2024:2985
- DLA-3331-1
- DLA-3331-2
- DLA-3922-1
- openSUSE-SU-2024:12681-1
- openSUSE-SU-2025:14739-1
- PYSEC-2023-11
- RHSA-2023:4693
- RHSA-2023:4971
- RHSA-2023:6615
- RHSA-2023:6793
- RHSA-2023:7096
- RHSA-2024:2985
- RLSA-2024:2985
- SUSE-SU-2023:0722-1
- SUSE-SU-2023:0722-2
- Published
- Feb 7, 2023
- Updated
- Jun 17, 2026
- EPSS
- 1.3% · 69th percentile
- CWE
- CWE-754
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.3%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 6.5
- CNA · GitHub_M
- 4.8
- 1.7 point gap
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| cryptography.io | cryptography | cpe:2.3:a:cryptography.io:cryptography |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- cryptography.io cryptography1.8 and later · before 39.0.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
pyca cryptography
- >=1.8, < 39.0.1affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | python3-cryptography | before 3.2.1-6.el8 | 3.2.1-6.el8 |
| AlmaLinux:8 | python39 | before 3.9.18-3.module_el8.10.0+3765+2f9a457d | 3.9.18-3.module_el8.10.0+3765+2f9a457d |
| AlmaLinux:8 | python39-attrs | before 20.3.0-2.module_el8.6.0+2780+a40f65e1 | 20.3.0-2.module_el8.6.0+2780+a40f65e1 |
| AlmaLinux:8 | python39-cffi | before 1.14.3-2.module_el8.6.0+2780+a40f65e1 | 1.14.3-2.module_el8.6.0+2780+a40f65e1 |
| AlmaLinux:8 | python39-cffi | before 1.14.3-2.module_el8.6.0+3248+c431e88c | 1.14.3-2.module_el8.6.0+3248+c431e88c |
| AlmaLinux:8 | python39-chardet | before 3.0.4-19.module_el8.6.0+2780+a40f65e1 | 3.0.4-19.module_el8.6.0+2780+a40f65e1 |
| AlmaLinux:8 | python39-cryptography | before 3.3.1-3.module_el8.10.0+3765+2f9a457d | 3.3.1-3.module_el8.10.0+3765+2f9a457d |
| AlmaLinux:8 | python39-Cython | before 0.29.21-5.module_el8.6.0+3248+c431e88c | 0.29.21-5.module_el8.6.0+3248+c431e88c |
| AlmaLinux:8 | python39-Cython | before 0.29.21-5.module_el8.6.0+2780+a40f65e1 | 0.29.21-5.module_el8.6.0+2780+a40f65e1 |
| AlmaLinux:8 | python39-debug | before 3.9.18-3.module_el8.10.0+3765+2f9a457d | 3.9.18-3.module_el8.10.0+3765+2f9a457d |
| AlmaLinux:8 | python39-devel | before 3.9.18-3.module_el8.10.0+3765+2f9a457d | 3.9.18-3.module_el8.10.0+3765+2f9a457d |
| AlmaLinux:8 | python39-idle | before 3.9.18-3.module_el8.10.0+3765+2f9a457d | 3.9.18-3.module_el8.10.0+3765+2f9a457d |
| AlmaLinux:8 | python39-idna | before 2.10-3.module_el8.6.0+2780+a40f65e1 | 2.10-3.module_el8.6.0+2780+a40f65e1 |
| AlmaLinux:8 | python39-iniconfig | before 1.1.1-2.module_el8.6.0+2780+a40f65e1 | 1.1.1-2.module_el8.6.0+2780+a40f65e1 |
| AlmaLinux:8 | python39-libs | before 3.9.18-3.module_el8.10.0+3765+2f9a457d | 3.9.18-3.module_el8.10.0+3765+2f9a457d |
| AlmaLinux:8 | python39-lxml | before 4.6.5-1.module_el8.6.0+3248+c431e88c | 4.6.5-1.module_el8.6.0+3248+c431e88c |
| AlmaLinux:8 | python39-lxml | before 4.6.5-1.module_el8.6.0+2780+a40f65e1 | 4.6.5-1.module_el8.6.0+2780+a40f65e1 |
| AlmaLinux:8 | python39-mod_wsgi | before 4.7.1-7.module_el8.9.0+3634+fb2a896c | 4.7.1-7.module_el8.9.0+3634+fb2a896c |
| AlmaLinux:8 | python39-more-itertools | before 8.5.0-2.module_el8.6.0+2780+a40f65e1 | 8.5.0-2.module_el8.6.0+2780+a40f65e1 |
| AlmaLinux:8 | python39-numpy | before 1.19.4-3.module_el8.6.0+2780+a40f65e1 | 1.19.4-3.module_el8.6.0+2780+a40f65e1 |
| AlmaLinux:8 | python39-numpy | before 1.19.4-3.module_el8.6.0+3248+c431e88c | 1.19.4-3.module_el8.6.0+3248+c431e88c |
| AlmaLinux:8 | python39-numpy-doc | before 1.19.4-3.module_el8.6.0+2780+a40f65e1 | 1.19.4-3.module_el8.6.0+2780+a40f65e1 |
| AlmaLinux:8 | python39-numpy-f2py | before 1.19.4-3.module_el8.6.0+2780+a40f65e1 | 1.19.4-3.module_el8.6.0+2780+a40f65e1 |
| AlmaLinux:8 | python39-numpy-f2py | before 1.19.4-3.module_el8.6.0+3248+c431e88c | 1.19.4-3.module_el8.6.0+3248+c431e88c |
+96
Same product
cryptography.io: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-36242In the cryptography package before 3.3.2 for Python, certain sequences of update calls to symmetrically encrypt multi-GB values could result38Monitor
- CVE-2026-26007cryptography Subgroup Attack Due to Missing Subgroup Validation for SECT Curves32Monitor
- CVE-2016-9243HKDF in cryptography before 1.5.2 returns an empty byte-string if used with a length less than algorithm.digest_size.31Monitor
- CVE-2024-26130cryptography NULL pointer deference with pkcs12.serialize_key_and_certificates when called with a non-matching certificate and private key and an hmac_hash over30Monitor
- CVE-2023-49083cryptography vulnerable to NULL-dereference when loading PKCS7 certificates30Monitor
- CVE-2023-38325The cryptography package before 41.0.2 for Python mishandles SSH certificates that have critical options.30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:python3-cryptography | 36.0.1-4.el9 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:python39 | 3.9.18-3.module_el8.10.0+3765+2f9a457d · AlmaLinux:8 | Package registry (OSV) |
| almalinux:python39-attrs | 20.3.0-2.module_el8.6.0+2780+a40f65e1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:python39-cffi | 1.14.3-2.module_el8.6.0+2780+a40f65e1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:python39-chardet | 3.0.4-19.module_el8.6.0+2780+a40f65e1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:python39-cryptography | 3.3.1-3.module_el8.10.0+3765+2f9a457d · AlmaLinux:8 | Package registry (OSV) |
| almalinux:python39-Cython | 0.29.21-5.module_el8.6.0+2780+a40f65e1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:python39-debug | 3.9.18-3.module_el8.10.0+3765+2f9a457d · AlmaLinux:8 | Package registry (OSV) |
| almalinux:python39-devel | 3.9.18-3.module_el8.10.0+3765+2f9a457d · AlmaLinux:8 | Package registry (OSV) |
| almalinux:python39-idle | 3.9.18-3.module_el8.10.0+3765+2f9a457d · AlmaLinux:8 | Package registry (OSV) |
| almalinux:python39-idna | 2.10-3.module_el8.6.0+2780+a40f65e1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:python39-PyMySQL | 0.10.1-2.module_el8.6.0+2780+a40f65e1 · AlmaLinux:8 | Package registry (OSV) |
| alpine:py3-cryptography | 39.0.1-r0 · Alpine:v3.23 | Package registry (OSV) |
| debian:python-cryptography | 38.0.4-3 · Debian:12 | Package registry (OSV) |
| opensuse:python-cryptography | 3.3.2-150400.16.6.1 · openSUSE:Leap Micro 5.3 | Package registry (OSV) |
| PyPI:cryptography | 39.0.1 | Package registry (OSV) |
| red hat:automation-eda-controller | 0:1.0.1-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:automation-eda-controller-server | 0:1.0.1-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:automation-eda-controller-ui | 0:1.0.1-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:python-cryptography | 0:38.0.4-2.el9ap · Red Hat:ansible_automation_platform_developer:2.4::el9 | Package registry (OSV) |
| red hat:python-cryptography-debugsource | 0:38.0.4-2.el9ap · Red Hat:ansible_automation_platform_developer:2.4::el9 | Package registry (OSV) |
| red hat:python3-cryptography | 0:38.0.4-2.el9ap · Red Hat:ansible_automation_platform_developer:2.4::el9 | Package registry (OSV) |
| red hat:python3-cryptography-debuginfo | 0:38.0.4-2.el9ap · Red Hat:ansible_automation_platform_developer:2.4::el9 | Package registry (OSV) |
| red hat:python39-cryptography | 0:38.0.4-2.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:python39-cryptography-debuginfo | 0:38.0.4-2.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:python39-requests | 0:2.31.0-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:python3x-cryptography | 0:38.0.4-2.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:python3x-cryptography-debugsource | 0:38.0.4-2.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| rocky linux:Cython | 0:0.29.21-5.module+el8.10.0+1582+bc278001 · Rocky Linux:8 | Package registry (OSV) |
| rocky linux:mod_wsgi | 0:4.7.1-7.module+el8.10.0+1582+bc278001 · Rocky Linux:8 | Package registry (OSV) |
+21
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- Low
Weakness class (CWE)
CWE-754 · Improper Check for Unusual or Exceptional ConditionsCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- github.com/pyca/cryptography/pull/8230/commits/94a50a9731f35405f0357fa5f3b177d46a726ab3
- lists.debian.org/debian-lts-announce/2024/10/msg00012.html
- security.netapp.com/advisory/ntap-20230324-0007/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.