LiveActive security incident?Get immediate response
CVE Record

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

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.

MediumCVSS 4.6Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-0519 is a medium-severity information disclosure issue in Absolute Secure Access. In certain configurations, logs may contain an unredacted authentication token. Anyone who can access those logs could reuse the token to access an integrated system. This is mainly a log access and credential hygiene risk, not a remotely exploitable takeover based on available sources.

Executive priority

Treat this as a targeted remediation item, not an emergency unless logs are broadly accessible or integrated systems are high value. Prioritize version validation, log access review, and token rotation if exposure is confirmed.

Technical view

The issue is CWE-532: insertion of sensitive information into log files. The CVSS 4.0 score is 4.6 with local access and high privileges indicated. Sources describe Secure Access 12.70 and versions prior to 14.20 as affected. Impact is limited confidentiality and integrity for the token’s integrated system; availability impact is not indicated.

Likely exposure

Organizations using Absolute Secure Access in the described affected range may be exposed if specific logging configurations are enabled and logs are accessible to administrators, SIEM users, support staff, or other parties.

Exploitation context

No active exploitation is indicated in the provided sources, and the CVE is not listed as KEV. Practical abuse requires access to logs containing an unredacted token. The main risk is token reuse against an integrated system after log exposure.

Researcher notes

Evidence is limited to the CVE record and vendor advisory reference. The CVSS vector indicates local access and high privileges, while the narrative says any log reader could reuse the token. Validate exact affected builds, configurations, and fixed releases directly against Absolute’s advisory.

Mitigation direction

  • Check Absolute’s advisory for the supported fixed version and configuration guidance.
  • Upgrade Secure Access out of the affected range where vendor guidance confirms remediation.
  • Restrict access to application, diagnostic, SIEM, and archived logs.
  • Review and reduce logging that may capture authentication material.
  • Rotate any tokens found in logs and invalidate old credentials.

Validation and detection

  • Inventory deployed Absolute Secure Access versions.
  • Confirm whether deployments match the affected range described by the advisory.
  • Review logging configuration for token-bearing authentication events.
  • Search retained logs for exposed authentication tokens using approved internal procedures.
  • Verify log access controls across servers, SIEM, backups, and support bundles.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-532: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-0519 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.6 (4.0)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.6CVSS 4.0MediumCVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

4.6Medium
CVSS 4.0 vector shape for CVE-2026-0519Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Absolute SecuritySecure Access12.70unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-532 · source CWE mapping

Insertion of Sensitive Information into Log File

Insertion of Sensitive Information into Log File represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.