Skip to main content
VulnerabilityPublished Updated

CVE-2026-115400: crawlseo · Cleartext Storage of Sensitive Information

Affects crawlseoSource CVE Database V5

0

Not known to be exploited · CVSS 6.7 Medium : upgrade to 0.2.5 when convenient.

Data as of 26 Oct 2026, 17:16 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

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

What to do

Upgrade crawlseo to 0.2.5.

Affected software

ProductAffectedFixed in
crawlseocrawlseoAffected
  • >=0.1.0 <0.2.5
Fixed in
  • 0.2.5
GitHubcrawlseopkg:github/crawlseoOther threatsAffected
  • >=0.1.0 <0.2.5
Fixed in
  • 0.2.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade crawlseo to version 0.2.5 or later, where the cleartext storage vulnerability has been fixed. No other mitigation is indicated by the vendor advisory.

Description

crawlseo versions prior to 0.2.5 store Google OAuth access and refresh tokens in cleartext within the database. This vulnerability allows attackers with read access to the Postgres database to obtain unencrypted tokens, enabling indefinite unauthorized access to users' Google Search Console data. The issue is fixed in version 0.2.5.

References

Community reviews

Loading reviews…