CVE-2025-2243: A server-side request forgery (SSRF) vulnerability in Bitdefender GravityZone Console allows an attacker to by

Q: How do I fix CVE-2025-2243?

gravityzone: upgrade to 6.41.2-1. Exact commands for each OS are on this page.

Q: Is CVE-2025-2243 being exploited?

CVE-2025-2243 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-2243 affect?

CVE-2025-2243 affects gravityzone. Severity is high (CVSS 7.3). A server-side request forgery (SSRF) vulnerability in Bitdefender GravityZone Console allows an attacker to bypass input validation logic using leading characters in DNS requests. Paired with other potential vulnerabilities, this bypass cou

Q: How urgent is CVE-2025-2243?

Priority 39/100. High severity; Remotely exploitable, no login, no user action

Routine

HIGH 7.3REMOTEUPGRADE

CVE-2025-2243 is a high-severity flaw (CVSS 7.3) affecting gravityzone. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A server-side request forgery (SSRF) vulnerability in Bitdefender GravityZone Console allows an attacker to bypass input validation logic using leading characters in DNS requests. Paired with other potential vulnerabilities, this bypass could be used for execution of third party code. This issue affects GravityZone Console: before 6.41.2.1.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.3 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 66%)
CISA exploited list	No
Weakness	CWE-918
Published	2025-04-04
Last modified	2026-06-17

Publisher (CNA): Bitdefender · Vendor: bitdefender

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-04-04 10:15 UTCPublished CVE record published
2026-06-17 09:06 UTCUpdated Record last modified

bitdefender gravityzone UPGRADE

Affected: < 6.41.2-1

Fixed in: 6.41.2-1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy gravityzone || rpm -q gravityzone || gravityzone --version

2. UPGRADE to 6.41.2-1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade gravityzone

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade gravityzone

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-2243?

gravityzone: upgrade to 6.41.2-1. Exact commands for each OS are on this page.

Is CVE-2025-2243 being exploited?

CVE-2025-2243 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-2243 affect?

CVE-2025-2243 affects gravityzone. Severity is high (CVSS 7.3). A server-side request forgery (SSRF) vulnerability in Bitdefender GravityZone Console allows an attacker to bypass input validation logic using leading characters in DNS requests. Paired with other potential vulnerabilities, this bypass cou

How urgent is CVE-2025-2243?

Priority 39/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2025-2244 CRITICAL 9.8 UPGRADE A vulnerability in the sendMailFromRemoteSource method in Emails.php as used in Bitdefender GravityZone Conso
CVE-2024-6980 CRITICAL 9.8 UPGRADE A verbose error handling issue in the proxy service implemented in the GravityZone Update Server allows an att
CVE-2024-4177 HIGH 8.1 UPGRADE A host whitelist parser issue in the proxy service implemented in the GravityZone Update Server allows an atta

References

← Back to latest CVEs