Urgent.News

One page, thousands of outlets. See who else covered it.

Editions

Tech

We scanned our own production site and found 8 vulnerabilities. Here’s the list.

Building software in 2026 feels surreal. With LLMs handling boilerplate, we ship features in hours that used to take weeks. But fast shipping has a nasty side effect: it breeds overconfidence. A few days ago, we ran an automated check against our own live marketing site ( vergate.dev ). We build security and diagnostic tools for a living, so we expected a clean bill of health. We were wrong. Our…

In 2026, software development seems almost magical, with artificial intelligence tools generating features in mere hours that once took weeks. However, this rapid pace has its downside, fostering an unwarranted sense of confidence. Recently, Vergate ran an automated security scan on their own live marketing site, vergate.dev, and discovered eight significant vulnerabilities.

While they expected a clean bill of health, the results were disheartening. The automated tool uncovered critical security issues, including missing security headers that left their site exposed to basic cross-site attacks. This incident underscores the importance of continuously measuring and automating security checks, as it's often embarrassing to realize how much can slip through the cracks when developing software in-house.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Designing HTML Page Caching Changed How I Think About Caching

Long Story Short Designing HTML page caching in practice connected several concepts I had previously understood separately, such as TTL, browser caching, and where cache policies should live.

  • HTML page caching at work revealed broader system impact
  • CloudFront served as CDN, cached HTML pages including SSR data
  • TTL wasn't simple, required context-specific reasoning

Building Resilient Background Jobs in NestJS with BullMQ

Background jobs look simple right up until one of them dies silently in production and nobody notices for three days. A job that sends confirmation emails stops running.

  • BullMQ tutorials focus on basics, lacking real-world resilience patterns
  • Implement exponential backoff with jitter to prevent thundering herd
  • Use idempotency keys to ensure retries are safe and avoid duplicates

More from Sunday 16 August →