PostgreSQL's 22-Year-Old Flaw and the IRC Server Under Active Attack: What UK Small Businesses Need to Know This Week

Cyber Security News

PostgreSQL's 22-Year-Old Flaw and the IRC Server Under Active Attack: What UK Small Businesses Need to Know This Week

CISA confirmed this week that attackers are actively exploiting a command injection flaw in UnrealIRCd. That confirmation does not come with a caveat. It means someone is using it, right now, on systems connected to the internet.

At the same time, PostgreSQL released its November 2026 security update, addressing 52 vulnerabilities and over 140 bugs. One of those vulnerabilities had been sitting in the codebase for 22 years.

These are the two stories that matter this week. Everything else is context.

The UnrealIRCd Flaw: Actively Exploited, CISA Confirmed

On the 14th of November 2026, CISA added CVE-2026-114713 to its Known Exploited Vulnerabilities catalogue. The flaw affects UnrealIRCd, an open-source Internet Relay Chat server used to run IRC networks.

The vulnerability allows server-level command injection. In plain language: an attacker who can reach the service can run commands on the underlying server as though they were sitting at the keyboard. That is not a nuanced, conditional risk. That is a full compromise path.

CISA’s KEV catalogue is not a theoretical watch list. Items land on it when there is evidence of active exploitation in the wild. CVE-2026-114713 is there because it is being used.

For most UK small businesses, the immediate question is whether you are running an UnrealIRCd instance anywhere. Many will not be. But the second question is more important: does your hosting provider, your MSP, or any third-party infrastructure you rely on run it? Supply chain exposure is not hypothetical. It is how most small business incidents actually start.

The week 46 CISA KEV roundup listed 12 exploited vulnerabilities across enterprise infrastructure, security gateways, and applications. CVE-2026-114713 was one of them. The volume of confirmed exploitations in a single week should recalibrate anyone’s assumption that attackers are selective.

They are not selective. They are automated.

PostgreSQL: 22 Years Is Not a Rounding Error

On the 12th of November 2026, PostgreSQL released its November security update. The release addressed 52 security vulnerabilities and more than 140 bugs across supported versions.

One of those vulnerabilities had existed in the codebase for 22 years.

That figure deserves a moment. PostgreSQL is one of the most widely deployed open-source relational databases in the world. It underpins web applications, internal tools, SaaS platforms, and business systems at every scale. The odds that software your business uses, directly or through a third party, does not touch PostgreSQL somewhere in its stack are lower than most people assume.

The CVEs associated with this release include CVE-2026-6467, CVE-2026-6460, CVE-2026-16237, and CVE-2026-14661. The 22-year-old flaw is the headline, but 52 vulnerabilities in a single release cycle is a material patching obligation, not a footnote.

For UK small businesses, the practical implication is not to become a PostgreSQL administrator overnight. It is to ask a specific question of whoever manages your infrastructure: has the November 2026 PostgreSQL update been applied? If the answer is not a confident yes with a date attached, that is a gap worth closing.

Why These Two Stories Together Matter

The combination of a confirmed active exploitation and a long-lived unpatched vulnerability in widely deployed software is not coincidental. It is the normal state of the threat landscape.

Attackers prioritise two categories of target: systems with known, exploitable vulnerabilities, and systems where the gap between patch release and patch application is long. Both stories this week speak directly to those categories.

UnrealIRCd operators who have not yet applied the fix for CVE-2026-114713 are, right now, sitting inside the first category. PostgreSQL installations running versions that predate the 12th of November 2026 update are sitting inside the second.

The NCSC’s guidance on vulnerability management is unambiguous on this point: critical and high-severity patches should be applied within 14 days of release for internet-facing systems. That is not a suggestion. For businesses holding personal data under UK GDPR, failure to apply known patches in a reasonable timeframe is a factor the ICO will consider when assessing whether a breach was preventable.

How to Turn This Into a Competitive Advantage

Patching is unglamorous. It does not make it into pitch decks. But it is one of the most visible signals of operational maturity that enterprise clients, procurement teams, and insurers actually check.

If your business can demonstrate a documented, timely patching process, with records showing that critical vulnerabilities were addressed within the NCSC’s recommended windows, that is a concrete differentiator in supplier assessments and tender processes. It is also the difference between an insurer paying out after an incident and an insurer pointing to negligence clauses.

The Cyber Essentials certification scheme requires patching of high-risk vulnerabilities within 14 days. If you hold that certification, this week’s PostgreSQL and UnrealIRCd updates are not optional extras. They are compliance obligations with a specific deadline.

Making the Business Case

Three points worth raising with whoever controls your IT budget:

The CISA KEV catalogue is public evidence of active harm. When a vulnerability appears on that list, it means real organisations are being compromised through it right now. CVE-2026-114713 is on that list as of the 14th of November 2026. Presenting that fact to a board or a senior manager is not fearmongering. It is reading the confirmed incident record.

A 22-year-old vulnerability in production software is an asset management failure, not a software failure. PostgreSQL fixed the bug. The question is whether your infrastructure applied the fix. That is an operational question, and the answer reflects directly on whoever is responsible for your IT.

UK GDPR creates a legal obligation to maintain appropriate technical measures. An unpatched known vulnerability on an internet-facing system, after a patch has been publicly released, is difficult to characterise as an appropriate technical measure. The ICO’s enforcement record shows they do look at patching timelines when investigating breaches.

What to Do Before the End of This Week

1. Ask your IT contact or MSP a direct question about PostgreSQL. The question is: has the November 2026 PostgreSQL security update been applied to all systems we operate or that hold our data? Request confirmation in writing, with a date.

2. Check for internet-facing IRC infrastructure. Most small businesses do not run UnrealIRCd. But if you host any kind of community platform, chat server, or legacy communications infrastructure, verify what software is running and whether it is current. If you do not know, ask your hosting provider.

3. Review your MSP’s patch management SLA. Does your contract specify how quickly critical vulnerabilities are patched? If it does not, raise it. If it does, verify that the PostgreSQL update falls within that window.

4. Check your Cyber Essentials status. If you hold Cyber Essentials or Cyber Essentials Plus certification, the 14-day patching requirement for high-risk vulnerabilities is a certification condition. Both updates this week fall within scope.

5. Document the conversation. If a breach occurs and you have written evidence that you asked the right questions and received confirmation of patching, your position with the ICO and your insurer is materially stronger than if you have no record at all.

None of this requires technical expertise. It requires asking specific questions and expecting specific answers.


Before you go: follow the show wherever you listen, leave a rating or review if it was useful, drop a comment with your thoughts, and share this with someone who needs to hear it. The small business owners who get this right are the ones who passed it on.

SourceArticle
The Hacker NewsAttackers Exploit UnrealIRCd Flaw That Enables Server-Level Command Injection
The Cyber ThronePostgreSQL fixes a 22-Year-Old Security Flaw
The Cyber ThroneCISA KEV Weekly Roundup: Week 46
CISA KEV CatalogueKnown Exploited Vulnerabilities Catalog
NCSCVulnerability management guidance
ICOSecurity (UK GDPR guidance)
NCSCCyber Essentials: overview

Filed under

  • smb-security
  • uk-business
  • incident-response
  • infrastructure-security
  • vendor-risk
  • compliance-failure
  • business-risk