CVE-2022-44268
ImageMagick 7.1.0-49 is vulnerable to Information Disclosure. When it parses a PNG image (e.g., for resize), the resulting image could have embedded the content of an arbitrary. file (if the magick binary has permissions to read it).
- CVSS
- 6.5Mediumscored by CISA
- Exploited in the wild
- Not knownPublic exploit code; not in CISA KEV
- EPSS
- 89.9%chance of exploitation in the next 30 daystop 0.3% of scored CVEsFIRST score of 11 Nov 2026
- Fix
- Not stated by the vendorno fixed release in the CVE record
- Published
- 6 Feb 2023analysed here 12 Nov 2026
Summary
Triage
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
Products named in our analysis
- imagemagick:imagemagick
Fix and mitigation
WAF and other mitigations
Can a WAF block it? Partly. Information exposure: some WAFs can scan responses and hide known leak patterns, such as stack traces or keys.
Also consider: response filtering
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Not listed as of our last sync.
- Public exploit code
- Yes: 1 on Exploit-DB · 30 GitHub proofs of concept
- CISA SSVC
- exploitation poc, automatable no, technical impact partialAssessed by CISA 26 Mar 2025 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
Exploit-DB
- ImageMagick 7.1.0-49 - Arbitrary File Readlocal, 5 Apr 2023
GitHub proofs of concept
- duc-nt/CVE-2022-44268-ImageMagick-Arbitrary-File-Read-PoC275 stars
- voidz0r/CVE-2022-44268218 stars
- Sybil-Scan/imagemagick-lfi-poc53 stars
- kljunowsky/CVE-2022-4426826 stars
and 26 more repositories
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
Timeline
- 2 Feb 2023First public exploit or proof of concept
- 6 Feb 2023Published5 days later
- 26 Mar 2025CISA SSVC assessment: exploitation poc779 days (about 2 years) later
- 26 Mar 2025CVE record last updatedsame day later
- 12 Nov 2026Analysed by vulneraibility.com596 days (about 2 years) later
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
| Metric | Value | What it means |
|---|---|---|
| Attack vector | NetworkReachable over the internet or any routable network. | Reachable over the internet or any routable network. |
| Attack complexity | LowRepeatable attack, no special conditions. | Repeatable attack, no special conditions. |
| Privileges required | NoneThe attacker needs no prior access. | The attacker needs no prior access. |
| User interaction | RequiredA victim must click, open or otherwise cooperate. | A victim must click, open or otherwise cooperate. |
| Scope | UnchangedImpact stays within the vulnerable component. | Impact stays within the vulnerable component. |
| Confidentiality | HighTotal data disclosure possible. | Total data disclosure possible. |
| Integrity | NoneNo unauthorised modification. | No unauthorised modification. |
| Availability | NoneThe service stays up. | The service stays up. |
Common questions
Is CVE-2022-44268 being exploited?
Not confirmed. CVE-2022-44268 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 90% probability of exploitation in the next 30 days.
How severe is CVE-2022-44268?
CVE-2022-44268 is rated Medium with a CVSS score of 6.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2022-44268?
Not known from our data. No patch reference has been recorded for CVE-2022-44268, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2022-44268 affect?
CVE-2022-44268 affects imagemagick:imagemagick. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
7 references in the CVE record, grouped by the tags the record gives them.
Advisories (3)
- debian.org /security/2023/dsa-5347
- lists.fedoraproject.org /archives/list/package-announce%40lists.fedoraproject.org/message/ZZLLS37P67CMBR
- lists.fedoraproject.org /archives/list/package-announce%40lists.fedoraproject.org/message/AINSUL2QBKETGY
Other links (4)
- imagemagick.org /
- metabaseq.com /imagemagick-zero-days/
- lists.debian.org /debian-lts-announce/2023/03/msg00008.html
- packetstormsecurity.com /files/171727/ImageMagick-7.1.0-48-Arbitrary-File-Read.html
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Exploit-DB: published exploits
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.