CVE-2025-52622: The BigFix SaaS's HTTP responses were missing some security headers
Source GCVE Database
Not known to be exploited · CVSS 5.4 Medium.
Data as of 22 Nov 2026, 02:44 UTC
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.
What to do
AI-suggested
As this is a configuration issue, remediation involves adding the appropriate security headers to HTTP responses to mitigate risks. Since this is not a cloud service, the responsibility for applying these headers lies with the application administrators. Monitor vendor advisories for any official guidance or updates.
Description
The BigFix SaaS application was found to have missing security headers in its HTTP responses. These headers are important for enhancing client-side security by mitigating risks such as Cross-Site Scripting (XSS), Clickjacking, and protocol downgrade attacks. The absence of these headers weakens the security posture of the application but does not directly indicate a vulnerability that allows remote code execution or data breach.