Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 GitHub Actions
Not in CISA KEV
CRITICAL severity

CVE-2023-50245 afichet/openexr-viewer

CRITICALFix: afichet/openexr-viewer@d0a7e85

CVE-2023-50245 is a critical-severity (CVSS 9.8) CWE-120 vulnerability in afichet/openexr-viewer. 1 public exploit reference exists, so weaponization risk is real. A fix is available for afichet/openexr-viewer — see the affected versions and patch details below.

OpenEXR-viewer memory overflow vulnerability

Also known asGHSA-99jg-r3f4-rpxj
Published
Dec 11, 2023
Updated
Aug 12, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Sep 21, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs62th percentile — riskier than 62% 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.

How urgent is this, really

CVE-2023-50245 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

1 pkg affected
📦afichet/openexr-viewer

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

Description

Just open this exr file through openexr-viewer.

( poc send by email )

This is windbg log file.

[ POC 2 ] (8660.7e44): Access violation - code c0000005 (!!! second chance !!!) openexr_viewer+0x27be4: 00007ff713ff7be4 c744880c0000803f mov dword ptr [rax+rcx*4+0Ch],3F800000h ds:0000020a3ac8000c=????????

Attempt to write the value 1.0 to the memory address 0x20A3AC8000C

[ POC 1 ] (1404.9264): Access violation - code c0000005 (first chance) First chance exceptions are reported before any exception handling. This exception may be expected and handled. openexr_viewer+0x27be4: 00007ff713ff7be4 c744880c0000803f mov dword ptr [rax+rcx*4+0Ch],3F800000h ds:0000029cb371600c=????????

Attempt to write the value 1.0 to the memory address 0x29CB371600C

Credits Team : ZeroPointer 이동하 ( Lee Dong Ha of ZeroPointer Lab ) 정지민    ( Jeong Jimin of ZeroPointer Lab ) 박우진    ( Park Woojin of ZeroPointer Lab ) 전우진    ( Jeon Woojin of ZeroPointer Lab )

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦GitHub Actionsafichet/openexr-viewerall versions0.6.1
Exploits & PoCs
1

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

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update afichet/openexr-viewer to 0.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-50245 is resolved across your whole dependency graph.

  3. Workarounds

    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.

  4. How O3 protects you

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

Tailored to CVE-2023-50245. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Just open this exr file through openexr-viewer. ( poc send by email ) This is windbg log file. [ POC 2 ] (8660.7e44): Access violation - code c0000005 (!!! second chance !!!) openexr_viewer+0x27be4: 00007ff7`13ff7be4 c744880c0000803f mov dword ptr [rax+rcx*4+0Ch],3F800000h ds:0000020a`3ac8000c=???????? Attempt to write the value 1.0 to the memory address 0x20A3AC8000C [ POC 1 ] (1404.9264): Access violation - code c0000005 (first chance) First chance exceptions are reported before any exception handling. This exception may be expected and handled. openexr_viewer+0x27be4: 00007ff7`13ff
O3 Security · Impact-Aware SCA

Is CVE-2023-50245 in your dependencies?

O3 Security finds CVE-2023-50245 across GitHub Actions dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2023-50245: afichet/openexr (Critical 9.8) | O3 Security