บันทึกการเปลี่ยนแปลง

May 18, 2026

• ใหม่electerm dependency advisory check. GitHub repo scans can now flag npm manifests and lockfiles that pin or allow electerm versions affected by CVE-2026-41500 / GHSA-wxw2-rwmh-vr8f, with version-based advisory evidence rather than exploit confirmation.
• ใหม่OpenCms dependency advisory check. GitHub repo scans can now flag Maven pom.xml files that pin or resolve org.opencms:opencms-core versions affected by CVE-2023-42344 / GHSA-rcc6-6q2f-m2cw, with version-based advisory evidence rather than XXE exploit confirmation.

May 17, 2026

• ใหม่FUXA hardcoded JWT secret check. Verified active scans can now confirm CVE-2025-69971 exposure on FUXA instances that still trust the vulnerable fallback JWT signing configuration.
• ใหม่CKAN DataStore SQL exposure check. Verified active scans can now confirm unauthenticated CKAN DataStore SQL access associated with CVE-2026-42031 and guide teams to patched CKAN release lines or safer DataStore configuration.

16 May 2026

• ใหม่PDF.js dependency advisory check. GitHub repo scans can now flag npm manifests and lockfiles that pin or allow pdfjs-dist versions affected by CVE-2024-4367 / GHSA-wgrm-67xf-hhpq.
• ใหม่Active scans via REST API and MCP. Active scans can now be triggered from REST and MCP against verified domains that have been explicitly authorized from the dashboard. Authorization is revocable at any time.
• ใหม่Safer authorization levels for active scans. Domain authorization now distinguishes safer automated active checks from deeper active testing, so teams can automate the right level of verification for each domain.
• ใหม่First-use webhook for API/MCP active scans. A webhook can notify teams the first time an API/MCP-triggered active scan runs against a newly authorized domain.
• ปรับปรุงImproved Referrer-Policy findings. Missing or weak Referrer-Policy results now separate URL-referrer leakage from broad information exposure, show document-response evidence, and include generic plus static-host remediation guidance.
• ปรับปรุงImproved Permissions-Policy findings. Missing or weak Permissions-Policy results now show feature-level evidence, separate broad feature allowlists from missing hardening, and include generic plus static-host remediation guidance for common hosts, proxies, and app servers.
• ปรับปรุงImproved clickjacking header prompts. Missing X-Frame-Options findings now point agents to CSP frame-ancestors as the modern protection, add Vercel/static SPA header guidance, and verify x-frame-options with CSP.
• ปรับปรุงCSP header evidence and fix prompts improved. Missing-CSP reports now include clearer hosting and response context plus safer framework-aware remediation guidance.
• แก้ไขVercel path-probe false positives reduced. FixVibe now requires stronger application-specific evidence before reporting exposed framework artifacts on deployments that rewrite unknown routes to the app shell.
• แก้ไขCompliance findings no longer carry misleading CWE tags. The legal-compliance check previously tagged "missing privacy policy" and "missing terms of service" findings with CWE-359 (PII exposure), which doesn't describe the actual gap. Those findings now ship without a CWE — they're compliance/governance items, not classifiable security weaknesses.

May 15, 2026

• ใหม่Additional research-informed checks. FixVibe shipped more coverage based on recent vulnerability research and mapped duplicate topics to existing scanner modules where coverage already existed.
• ใหม่Repository secret leak check. GitHub repo scans can now flag hardcoded provider keys and high-entropy secret-like values committed to source, with evidence masked and the standard FixVibe rotation prompt included.
• ใหม่Vercel deployment protection check. Passive scans can now flag public *.vercel.app generated deployment URLs that respond without Vercel Deployment Protection, while existing header checks continue to audit CSP, HSTS, and browser hardening.

May 14, 2026

• ใหม่LiteLLM dependency advisory check. GitHub repo scans can now flag Python dependency files that pin or allow LiteLLM versions affected by CVE-2026-42208 / GHSA-r75f-5x8p-qvmc.
• ใหม่LibreNMS dependency advisory check. GitHub repo scans can now flag Composer manifests that pin or allow LibreNMS versions affected by CVE-2024-51092 / GHSA-x645-6pf9-xwxw.
• ปรับปรุงFirebase rules detection improved. BaaS scans now detect more Firebase app shapes and use read-only evidence to identify risky public data exposure.

May 13, 2026

• ใหม่Repo Supabase RLS migration check. GitHub repo scans can now flag Supabase SQL migrations that create public tables without a matching ALTER TABLE ... ENABLE ROW LEVEL SECURITY statement.
• ใหม่Supabase Storage posture check. Passive scans can now review public Supabase Storage buckets and anonymous object-listing exposure alongside existing RLS and key checks.
• ใหม่AI-generated code guardrail check. GitHub repo scans can now flag missing security automation around code scanning, secret scanning, dependency updates, and AI-agent instructions.

May 12, 2026

• ใหม่Repo web-app risk checklist. GitHub repo scans can now flag high-confidence OWASP-style code risks such as raw SQL interpolation, unsafe HTML sinks, credentialed wildcard CORS, disabled TLS verification, and weak JWT secret fallbacks.
• ใหม่Next.js middleware-bypass check. Active scans for verified domains can now confirm CVE-2025-29927 exposure on middleware-protected routes before reporting it, and reports include the standard FixVibe AI fix prompt for remediation.

9 พฤษภาคม 2026

• ความปลอดภัยCross-origin scope hardening. Active scans and client-asset checks now stay within the authorized target scope and avoid carrying customer-provided credentials across cross-origin redirects.
• แก้ไขSupabase RLS check is now strictly read-only. Supabase posture checks now avoid write attempts and focus on safe exposure signals. Verified-domain active testing remains the boundary for deeper confirmation.
• ปรับปรุงSecurity-header findings ใช้กับ root HTML responses เท่านั้น. การขาด CSP, Permissions-Policy, X-Frame-Options หรือ Referrer-Policy บน 204, JSON API, file download หรือ 404 จะไม่สร้าง finding อีก HSTS และ X-Content-Type-Options ยังคง grade ทุก response
• ปรับปรุงAuth-flow and rate-limit checks now require stronger evidence. FixVibe now reports these issues only when the application behavior clearly supports the finding, reducing noise from generic error pages and unsupported methods.
• ปรับปรุงFile-upload findings tier by exploitability evidence. File-upload reports now separate low-confidence acceptance signals from stronger evidence of risky serving behavior, reducing over-severity on benign upload handlers.

7 พฤษภาคม 2026

• แก้ไขThreat-intel listing accuracy improved. FixVibe now distinguishes real blocklist evidence from resolver diagnostics so threat-intel findings do not over-report on infrastructure-side lookup responses.
• ใหม่GitHub repo scans. เชื่อมต่อ repo แล้ว FixVibe ตรวจ source เพื่อหา Supabase service keys ที่รั่ว, Firebase admin tokens, workflow files เสี่ยง และ dependencies ที่ล้าสมัย — โดยไม่โหลด deployed site ของคุณเลย ดู ประเภทการสแกน
• ใหม่SAST checks สำหรับ JavaScript เสี่ยง. Repo scans ตอนนี้ flag new Function() และ setTimeout("string") — ทั้งคู่เทียบเท่า eval() เมื่อป้อน input ที่ไม่น่าเชื่อถือ
• แก้ไขFalse “exposed file” findings บนไซต์ Vercel / Cloudflare. response 403 Forbidden เปล่าๆ จะไม่ถูกรายงานเป็น “file exists” อีก — edge providers ส่วนใหญ่คืน 403 สำหรับ path ที่ดูน่าสงสัยไม่ว่า file จะมีอยู่หรือไม่ ตอนนี้เราต้องมี positive HTTP signal ก่อน flag
• แก้ไขRepo-code false positives reduced. Repo scans now avoid flagging security terms in comments, documentation, test helpers, and clearly server-only contexts for several high-signal code checks.
• แก้ไขSupabase anon key ใน localStorage ไม่ถูกรายงานเป็น JWT-in-storage finding อีก — anon key คือ client token ที่ตั้งใจให้เปิดเผย public Service-role tokens จริงใน browser storage ตอนนี้เป็น critical พร้อม title ที่ชัดขึ้น
• แก้ไขCSP weakness detection improved. Content-Security-Policy checks now catch more permissive source policies while keeping evidence and remediation focused on the effective browser policy.
• แก้ไขReflected-XSS check tightened. Active scans now require stronger reflection evidence before reporting executable-context risk, reducing false positives from unrelated markup on the page.
• แก้ไขDomain verification จัดการ apex ↔ www redirects ได้ถูกต้อง และชัดขึ้นว่าค่าใดต้องใส่ใน TXT-record Host field

รูปแบบ

แต่ละรายการมี tag เพื่อให้คุณกวาดอ่านได้:

• ใหม่ Check, surface หรือ feature ใหม่
• ปรับปรุง พฤติกรรมเดิมดีขึ้น — แม่นขึ้น เร็วขึ้น ชัดขึ้น
• แก้ไข บั๊กที่เราเคย ship แล้วแก้ไข
• ความปลอดภัย การ hardening, vulnerability fixes หรือ compliance changes

เห็นสิ่งที่เสียและยังไม่ได้บันทึกไว้ที่นี่? Email support@fixvibe.app