CVE-2023-2840 [Critical] | Security Vulnerability in Gpac

CVE-2023-2840 is rated High Exploit Risk (70.8/100): CVSS Critical severity, with low exploitation likelihood (EPSS 0.65%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

EDB-ID	Source	Kind	Published	Link
—	nvd_ref	exploit_tag		Exploit-DB ↗

EDB-ID

Source

Kind

Published

Link

—

nvd_ref

exploit_tag

Exploit-DB ↗

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.26%	0.65%	+0.39%
2	2026-06-06	0.38%	0.26%	-0.12%
3	2026-06-04	—	0.38%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.26%

0.65%

+0.39%

2026-06-06

0.38%

0.26%

-0.12%

2026-06-04

—

0.38%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
9.8	3.1	CRITICAL	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	3.9	5.9	[email protected]
5.3	3.0	MEDIUM	`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:L) Some sensitive info could get out, but not a total data dump. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:L) Might cause slowdowns, glitches, or partial disruption—not a full brick.	1.8	3.4	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

9.8

3.1

CRITICAL

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

3.9

5.9

[email protected]

5.3

3.0

MEDIUM

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L): Might cause slowdowns, glitches, or partial disruption—not a full brick.

1.8

3.4

[email protected]

OS Trackers for CVE-2023-2840

vendor	priority	summary	link
`debian`	end-of-life	CVE-2023-2840 end-of-life priority: Debian including 1 source packages (gpac), 1 status rows across 1 suites (bullseye): open 1.	https://security-tracker.debian.org/tracker/CVE-2023-2840
`ubuntu`	medium	CVE-2023-2840 medium priority: Ubuntu including 1 source packages (gpac), 13 status rows across 13 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): needs-triage 7, DNE 4, ignored 2.	https://ubuntu.com/security/CVE-2023-2840

Affected software / configurations for CVE-2023-2840

Vendor	Product	Version	Raw CPE
gpac	gpac	< 2.2.1	cpe:2.3:a:gpac:gpac::::::::

References for CVE-2023-2840

URL	Tags
https://github.com/gpac/gpac/commit/ba59206b3225f0e8e95a27eff41cb1c49ddf9a37	Patch
https://huntr.dev/bounties/21926fc2-6eb1-4e24-8a36-e60f487d0257	Exploit Patch
https://www.debian.org/security/2023/dsa-5411

URL

CVE-2023-2840 | NULL Pointer Dereference in gpac/gpac

Public exploit references (Exploit-DB) for CVE-2023-2840

Exploit prediction scoring system (EPSS) score for CVE-2023-2840

Common vulnerability scoring system (CVSS) metrics for CVE-2023-2840

Weakness enumeration for CVE-2023-2840

OS Trackers for CVE-2023-2840

Affected software / configurations for CVE-2023-2840

References for CVE-2023-2840