CVE-2025-52621: HCL BigFix SaaS Authentication Service is vulnerable to cache poisoning

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

bigfix saas: upgrade to 8.1.14. Exact commands for each OS are on this page.

Q: Is CVE-2025-52621 being exploited?

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

CVE-2025-52621 affects bigfix saas. Severity is medium (CVSS 5.3). HCL BigFix SaaS Authentication Service is vulnerable to cache poisoning. The BigFix SaaS's HTTP responses were observed to include the Origin header. Its presence alongside an unvalidated reflection of the Origin header value introduces a

Q: How urgent is CVE-2025-52621?

Priority 25/100. Remotely exploitable, no login, no user action

Routine

MEDIUM 5.3REMOTEUPGRADE

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

HCL BigFix SaaS Authentication Service is vulnerable to cache poisoning. The BigFix SaaS's HTTP responses were observed to include the Origin header. Its presence alongside an unvalidated reflection of the Origin header value introduces a potential for cache poisoning.

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.2% (top 96%)
CISA exploited list	No
Weakness	CWE-346
Published	2025-08-15
Last modified	2026-06-17

Publisher (CNA): HCL Software · Vendor: hcltech

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

Am I affected?

Timeline

2025-08-15 23:15 UTCPublished CVE record published
2026-06-17 09:36 UTCUpdated Record last modified

hcltech bigfix saas UPGRADE

Affected: < 8.1.14

Fixed in: 8.1.14

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy bigfix-saas || rpm -q bigfix-saas || bigfix-saas --version

2. UPGRADE to 8.1.14 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade bigfix-saas

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade bigfix-saas

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

bigfix saas: upgrade to 8.1.14. Exact commands for each OS are on this page.

Is CVE-2025-52621 being exploited?

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

CVE-2025-52621 affects bigfix saas. Severity is medium (CVSS 5.3). HCL BigFix SaaS Authentication Service is vulnerable to cache poisoning. The BigFix SaaS's HTTP responses were observed to include the Origin header. Its presence alongside an unvalidated reflection of the Origin header value introduces a

How urgent is CVE-2025-52621?

Priority 25/100. Remotely exploitable, no login, no user action

Related CVEs

CVE-2025-52620 MEDIUM 4.3 UPGRADE HCL BigFix SaaS Authentication Service is affected by a Cross-Site Scripting (XSS) vulnerability
CVE-2025-52619 MEDIUM 5.3 UPGRADE HCL BigFix SaaS Authentication Service is affected by a sensitive information disclosure
CVE-2025-52618 MEDIUM 4.3 UPGRADE HCL BigFix SaaS Authentication Service is affected by a SQL injection vulnerability

References

← Back to latest CVEs