Skip to main content
CVE-2026-0519VulnerabilityPublished Updated

CVE-2026-0519: Absolute Security Secure Access · Sensitive Data in Logs

Affects Absolute Security Secure AccessSource CVE Database V5

0

Not known to be exploited · CVSS 4.6 Medium : upgrade to 14.20 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
4.6Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 14.20
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-25.

What to do

Upgrade Absolute Security Secure Access to 14.20.

Affected software

ProductAffectedFixed in
Absolute SecuritySecure AccessAffected
  • >=12.70 <14.20
Fixed in
  • 14.20

AI-suggested

European organizations should immediately audit and restrict access to log files generated by Secure Access to only the minimum necessary personnel. Review and adjust logging configurations to ensure authentication tokens are redacted or not logged at all. Implement strict file system permissions and monitoring on log storage locations to detect unauthorized access attempts. Until patches or updates are available, consider upgrading to Secure Access versions 14.20 or later once released by Absolute Security. Employ additional compensating controls such as multi-factor authentication (MFA) on integrated systems to reduce the impact of token compromise. Conduct regular security awareness training for administrators regarding secure log handling. Finally, establish incident response procedures to quickly revoke and rotate authentication tokens if exposure is suspected.

Description

In Secure Access 12.70 and prior to 14.20, the logging subsystem may write an unredacted authentication token to logs under certain configurations. Any party with access to those logs could read the token and reuse it to access an integrated system.

References

Community reviews

Loading reviews…