Izmaiņu žurnāls

May 18, 2026

• JAUNSelecterm 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.
• JAUNSOpenCms 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.
• JAUNSMagicMirror /cors SSRF check. Verified active scans can now confirm CVE-2026-42281 exposure on MagicMirror instances when the unauthenticated /cors endpoint fetches a FixVibe-controlled external callback, without probing internal services.

May 17, 2026

• JAUNSFUXA 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.
• JAUNSCKAN 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

• JAUNSPDF.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.
• JAUNSActive 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.
• JAUNSSafer 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.
• JAUNSFirst-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.
• UZLABOTSImproved 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.
• UZLABOTSImproved 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.
• UZLABOTSImproved 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.
• UZLABOTSCSP header evidence and fix prompts improved. Missing-CSP reports now include clearer hosting and response context plus safer framework-aware remediation guidance.
• LABOTSVercel 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.
• LABOTSCompliance 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

• JAUNSAdditional research-informed checks. FixVibe shipped more coverage based on recent vulnerability research and mapped duplicate topics to existing scanner modules where coverage already existed.
• JAUNSRepozitorija noslēpumu noplūdes pārbaude. GitHub repozitorija skenēšana tagad var atzīmēt avota kodā nosūtītus cietkodētus pakalpojumu sniedzēja atslēgas un augstas entropijas noslēpumam līdzīgas vērtības — ar maskētiem pierādījumiem un standarta FixVibe rotācijas uzaicinājumu.
• JAUNSVercel 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

• JAUNSLiteLLM 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.
• JAUNSLibreNMS 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.
• UZLABOTSFirebase 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

• JAUNSRepo 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.
• JAUNSSupabase Storage posture check. Passive scans can now review public Supabase Storage buckets and anonymous object-listing exposure alongside existing RLS and key checks.
• JAUNSAI-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

• JAUNSRepo 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.
• JAUNSNext.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.

2026. gada 9. maijs

• DROŠĪBACross-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.
• LABOTSSupabase 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.
• UZLABOTSDrošības galveņu atradumi attiecas tikai uz saknes HTML atbildēm. Trūkstošs CSP, Permissions-Policy, X-Frame-Options vai Referrer-Policy uz 204, JSON API, faila lejupielādes vai 404 vairs nerada atradumu. HSTS un X-Content-Type-Options joprojām tiek vērtēti visās atbildēs.
• UZLABOTSAuth-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.
• UZLABOTSFile-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.

2026. gada 7. maijs

• LABOTSThreat-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.
• JAUNSGitHub repo skenēšanas. Savienojiet repo, un FixVibe pārbaudīs avotu uz noplūdušām Supabase service keys, Firebase admin tokeniem, riskantiem workflow failiem un novecojušām atkarībām, nekad neielādējot jūsu izvietoto vietni. Skatiet Skenēšanas tipi.
• JAUNSSAST pārbaudes riskantam JavaScript. Repo skenēšanas tagad atzīmē new Function() un setTimeout("string"); abi ir līdzvērtīgi eval(), kad tiem padod neuzticamu ievadi.
• LABOTSViltus “exposed file” atradumi Vercel / Cloudflare vietnēs. Vienkāršas 403 Forbidden atbildes vairs netiek ziņotas kā “file exists”; vairums edge pakalpojumu sniedzēju atgriež 403 aizdomīgiem ceļiem neatkarīgi no tā, vai fails tur ir. Tagad pirms atzīmēšanas prasām pozitīvu HTTP signālu.
• LABOTSRepo-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.
• LABOTSSupabase anon key localStorage vairs netiek ziņots kā JWT-in-storage atradums; anon key ir publiski paredzēts klienta tokens. Īsti service-role tokeni pārlūka glabātuvē tagad ir critical ar skaidrāku nosaukumu.
• LABOTSCSP weakness detection improved. Content-Security-Policy checks now catch more permissive source policies while keeping evidence and remediation focused on the effective browser policy.
• LABOTSReflected-XSS check tightened. Active scans now require stronger reflection evidence before reporting executable-context risk, reducing false positives from unrelated markup on the page.
• LABOTSDomēna pārbaude pareizi apstrādā apex ↔ www pāradresācijas un skaidrāk norāda, kura vērtība jāliek TXT ieraksta Host laukā.

Formāts

Katrs ieraksts ir marķēts, lai varētu ātri pārskatīt:

• JAUNS Jauna pārbaude, virsma vai funkcija.
• UZLABOTS Esošā uzvedība kļuva labāka: precīzāka, ātrāka, skaidrāka.
• LABOTS Kļūda, ko izlaidām un pēc tam salabojām.
• DROŠĪBA Pastiprināšana, ievainojamību labojumi vai atbilstības izmaiņas.

Pamanījāt kaut ko salūzušu, kas šeit nav ierakstīts? Rakstiet support@fixvibe.app.