CVE-2025-52613: HCL BigFix Service Management (SM) is affected by use of a vulnerable WSGI Server was identified

Routine

MEDIUM 4.6DOWNGRADE

CVE-2025-52613 is a medium-severity flaw (CVSS 4.6) affecting bigfix service management. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

HCL BigFix Service Management (SM) is affected by use of a vulnerable WSGI Server was identified. Deploying an outdated or insecure WSGI server may expose the application to known security weaknesses, potentially increasing the risk of exploitation and unauthorized access.

Why this priority

No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	4.6 (Medium)
Attack vector	Adjacent network
Attack complexity	High
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.2% (top 86%)
CISA exploited list	No
Weakness	CWE-200
Published	2026-05-06
Last modified	2026-10-07

Publisher (CNA): HCL Software · Vendor: hcltech

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

Am I affected?

Timeline

2026-05-06 15:16 UTCPublished CVE record published
2026-10-07 09:10 UTCUpdated Record last modified

hcltech bigfix service management DOWNGRADE

Affected: 23.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 23.0

1. Check installed version

apt-cache policy bigfix-service-management || rpm -q bigfix-service-management || bigfix-service-management --version

2. No fixed release: DOWNGRADE to a release before 23.0 (Debian / Ubuntu)

apt-cache madison bigfix-service-management sudo apt install bigfix-service-management=<VERSION_BEFORE_23.0> sudo apt-mark hold bigfix-service-management

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list bigfix-service-management sudo dnf downgrade bigfix-service-management-<VERSION_BEFORE_23.0> sudo dnf versionlock add bigfix-service-management

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

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-52613?

bigfix service management: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2025-52613 being exploited?

CVE-2025-52613 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-52613 affect?

CVE-2025-52613 affects bigfix service management. Severity is medium (CVSS 4.6). HCL BigFix Service Management (SM) is affected by use of a vulnerable WSGI Server was identified. Deploying an outdated or insecure WSGI server may expose the application to known security weaknesses, potentially increasing the risk of expl

How urgent is CVE-2025-52613?

Priority 20/100. No elevated risk signals yet.

Related CVEs

CVE-2026-56590 MEDIUM 6.4 DOWNGRADE HCL BigFix Service Management is affected by an Unrestricted File Upload vulnerability due to improper file va
CVE-2026-21848 MEDIUM 5.0 DOWNGRADE HCL BigFix Service Management is affected by a Security Misconfiguration vulnerability, which could allow an a
CVE-2026-56592 MEDIUM 6.5 DOWNGRADE HCL BigFix Service Management is affected by an Improper Authentication validation vulnerability related to in
CVE-2026-56595 LOW 3.1 DOWNGRADE HCL BigFix Service Management is affected by a CORS Misconfiguration vulnerability due to improperly validated
CVE-2026-56597 LOW 3.1 DOWNGRADE HCL BigFix Service Management is affected by a Sensitive Information Leakage vulnerability, which could allow

References

← Back to latest CVEs