How severe is GHSA-q7pp-wcgr-pffx?

No CVSS score has been assigned to GHSA-q7pp-wcgr-pffx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-q7pp-wcgr-pffx?

GHSA-q7pp-wcgr-pffx affects the following packages: github.com/disintegration/imaging (Go). Ecosystems affected: Go.

How do I fix GHSA-q7pp-wcgr-pffx?

No patched version of github.com/disintegration/imaging has shipped for GHSA-q7pp-wcgr-pffx yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-q7pp-wcgr-pffx in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/disintegration/imaging, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-q7pp-wcgr-pffx if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-q7pp-wcgr-pffx?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-q7pp-wcgr-pffx can be triaged on real exposure rather than presence alone.

Is GHSA-q7pp-wcgr-pffx actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-q7pp-wcgr-pffx, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-q7pp-wcgr-pffx?

GHSA-q7pp-wcgr-pffx has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 32th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-q7pp-wcgr-pffx?

GHSA-q7pp-wcgr-pffx is classified as CWE-129 (CWE-129). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-q7pp-wcgr-pffx published, and has it been updated?

GHSA-q7pp-wcgr-pffx was published on September 5, 2023 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

GHSA-q7pp-wcgr-pffx — imaging

GHSA-q7pp-wcgr-pffx is a CWE-129 vulnerability in github.com/disintegration/imaging. 1 public exploit reference exists, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

Crash when processing crafted TIFF files

Also known asCVE-2023-36308

Published

Sep 5, 2023

Updated

Sep 10, 2026

Affected

1 pkg

Patched

None yet

Exploits

1 known

Exploitation data as of Sep 21, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-q7pp-wcgr-pffx.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs32th percentile — riskier than 32% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

🐹github.com/disintegration/imaging

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Disintegration Imaging 1.6.2 allows attackers to cause a panic (because of an integer index out of range during a Grayscale call) via a crafted TIFF file to the scan function of scanner.go. NOTE: it is unclear whether there are common use cases in which this panic could have any security consequence

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/disintegration/imaging`	all versions	No fix

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

disintegration Imaging 1.6.2 allows attackers to cause a panic (because …

github.comNVDSep 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/disintegration/imaging, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of github.com/disintegration/imaging has shipped for GHSA-q7pp-wcgr-pffx yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-q7pp-wcgr-pffx can be triaged on real exposure rather than presence alone.

Tailored to GHSA-q7pp-wcgr-pffx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-q7pp-wcgr-pffx in your dependencies?

O3 Security finds GHSA-q7pp-wcgr-pffx across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works