CVE-2026-115400 crawlseo CVE debrief

Who should care

Defenders responsible for systems using crawlseo, particularly those with access to the database or Google Search Console data, should assess exposure and apply the patch. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify inventory, assess exposure, and apply the vendor-provided patch to prevent unauthorized access to Google Search Console data.

Why it matters

CVE-2026-115400 allows attackers to obtain Google OAuth tokens, potentially leading to unauthorized access to Google Search Console data. Defenders should verify inventory, assess exposure, and apply the vendor-provided patch.

• Obtain Google OAuth access and refresh tokens
• Gain indefinite, unauthenticated access to Google Search Console data
• Read plaintext long-lived refresh tokens from a compromised or exposed Postgres database

Technical summary

The crawlseo package before version 0.2.5 stores Google OAuth access and refresh tokens in cleartext in the User.googleTokens column of the database. This allows attackers with database read access to obtain these tokens and gain indefinite, unauthenticated access to all registered users' Google Search Console data. The vulnerability is a cleartext storage issue that can be exploited by reading the plaintext long-lived refresh tokens from a compromised or exposed Postgres database. Defenders should prioritize verifying inventory, assessing exposure, and applying the vendor-provided patch.

Defensive priority

Defenders should prioritize verifying inventory, assessing exposure, and applying the vendor-provided patch.

Recommended defensive actions

• Verify inventory of systems using crawlseo and assess exposure
• Apply the vendor-provided patch to update to version 0.2.5 or later
• Monitor for unauthorized access to Google Search Console data
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability was reported in the crawlseo package before version 0.2.5. The CVE Program and NVD provide official records of the issue. The vulnerability allows attackers with database read access to obtain Google OAuth access and refresh tokens stored unencrypted in the User.googleTokens column. Evidence is based on official CVE and NVD records, as well as vendor-provided patch and release notes.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.