Skip to main content
VulnerabilityPublished

CVE-2025-63729: Sensitive Data in Logs

Source CVE Database V5

0

Not known to be exploited · CVSS 9.0 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.09% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Nov 2025

  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 26 Oct 2026.

What to do

AI-suggested

  1. Immediate network segmentation to isolate Syrotech SY-GPON-1110-WDONT devices from sensitive network segments and limit access to management interfaces.
  2. Implement strict access controls and monitoring on device management ports and protocols to detect unauthorized access attempts.
  3. Conduct thorough inventory and assessment to identify all deployed devices running the vulnerable firmware version.
  4. Engage with Syrotech or authorized vendors to obtain firmware updates or patches addressing this vulnerability as soon as they become available.
  5. If firmware updates are not immediately available, consider temporary mitigations such as disabling remote management or restricting it to trusted IP addresses.
  6. Employ network intrusion detection systems (NIDS) to monitor for anomalous traffic patterns indicative of exploitation attempts.
  7. Regularly audit device configurations and logs for signs of compromise.
  8. Educate operational teams about the vulnerability and ensure incident response plans include scenarios involving compromised cryptographic materials.
  9. Explore cryptographic key rotation policies and certificate revocation procedures to limit the impact if keys are compromised.
  10. Collaborate with upstream ISPs and vendors to share threat intelligence and coordinate response efforts.

Description

An issue was discovered in Syrotech SY-GPON-1110-WDONT SYRO_3.7L_3.1.02-240517 allowing attackers to exctract the SSL Private Key, CA Certificate, SSL Certificate, and Client Certificates in .pem format in firmware in etc folder.

References

Community reviews

Loading reviews…