Thursday’s technology rundown spans an urgent security deadline, a resolved AI-service interruption, a major health-data breach update, and two genuinely free PC games. The common thread is simple: verify the current state before you patch, troubleshoot, freeze credit, or click “buy.”
Reporting cutoff: August 27, 2026, 5:15 p.m. EDT (21:15 UTC). CISA’s catalog confirms known exploitation but does not identify victims or attackers. GitHub’s Kimi K3 incident is resolved, with a deeper analysis still pending. Baylor Genetics has described the incident and affected data categories; the 2.81 million count is attributed to Hearst Television’s report of the federal filing. Epic’s U.S. promotion feed shows both games at $0 through September 3. The featured image reads “AUGUST 27, 2026” and “THE IT GUYS”; its abstract technology symbols are editorial context, not evidence of a specific vendor or incident.
Listen to the broadcast-ready recap
This KittenTTS Bella narration was synthesized locally from the same checked facts as the article.
Tonight’s four-story rundown
1. Six known-exploited vulnerabilities demand inventory before panic
CISA’s live Known Exploited Vulnerabilities catalog lists six additions dated August 26 across NetScaler, Microsoft SQL Server, Ajax.NET Professional, the Linux kernel, Red Hat libuser, and Red Hat ABRT.[1] The catalog assigns August 29 remediation due dates to NetScaler CVE-2026-8452 and SQL Server CVE-2019-1068; the other four carry September 9 dates.[1]
Those dates are federal operational deadlines under CISA directives, not universal legal deadlines for every private organization. KEV inclusion means CISA has evidence of exploitation in the wild, but the catalog marks known ransomware-campaign use as “Unknown” for all six and does not name victims, attackers, campaign size, or compromise at any particular organization.[1]
Practical context: inventory exposed NetScaler appliances and affected SQL Server branches first, preserve evidence if compromise is suspected, then test vendor-supported remediation with rollback. For local Linux flaws, prioritize systems where untrusted users or processes can reach the vulnerable component.
2. GitHub’s Kimi K3 Copilot interruption is resolved
GitHub’s incident record says Kimi K3 was degraded in Copilot products and IDE surfaces because of an issue with an unnamed upstream model provider. GitHub marked the incident resolved at 8:12 a.m. EDT on August 27 and said the model was available again.[2]
The historical incident retained a critical-impact label, while GitHub’s live component state returned to operational. GitHub has not yet published the provider identity, affected-user share, error rate, regions, or detailed root cause; its incident note says a deeper analysis will follow.[2]
Practical context: if Kimi K3 still fails, check GitHub Status for a new incident, retry once, compare Auto or another model, and preserve unsaved work before changing extensions or local settings.
3. Baylor Genetics breach reporting reaches 2.81 million people
Baylor Genetics says an unauthorized third party accessed parts of its network and data between June 11 and June 17, 2026. The company says it identified suspicious activity around June 15, secured affected systems, and completed its review of potentially affected information around July 30.[3]
Hearst Television reports that Baylor Genetics told the U.S. Department of Health and Human Services approximately 2,810,878 people were affected.[4] That nationwide figure is attributed to Hearst’s report of the filing; this edition did not independently export the specific HHS portal row. Baylor says information varied by person and may have included names, dates of birth, medical testing information, laboratory results, health-insurance information, and Social Security numbers for what it calls a very limited subset.[3]
Practical context: affected people should verify a notice independently, use Baylor’s official contact information, review explanation-of-benefits records, consider a free credit freeze, and avoid links or phone numbers in unexpected messages claiming to offer breach help.[5]
4. Epic’s two PC giveaways are free to keep—not a weekend trial
Epic’s live U.S. promotions feed shows Breathedge and Rival Stars Horse Racing: Desktop Edition as qualifying base-game offers reduced from $24.99 each to $0 from August 27 at 11 a.m. EDT through September 3 at 11 a.m. EDT.[6] A completed $0 checkout adds the claimed game to that Epic account; leaving a store page open does not reserve the promotion.
Breathedge is a humorous single-player space-survival and crafting game, while Rival Stars Horse Racing: Desktop Edition centers on stable management, breeding, training, and racing.[7][8] The combined regular U.S. list price is $49.98, but that arithmetic is not a claim about personal value or future resale value.
Practical context: confirm the checkout total is exactly $0, use the official Epic site or launcher, and remember that claiming a game does not mean every computer meets its storage or hardware requirements.
What to do next
- Security teams: match the six KEVs to real inventory, exposure, vendor guidance, evidence-preservation needs, and rollback.
- Copilot users: verify live status before reinstalling extensions or changing accounts.
- Baylor patients and workforce: verify notices, freeze credit when appropriate, monitor medical and insurance records, and distrust unsolicited “help.”
- PC gamers: complete both $0 checkouts before September 3 at 11 a.m. EDT and secure the Epic account with multifactor authentication.
Need help with security, recovery, accounts, or a stubborn computer? Schedule The IT Guys
More from The IT Guys today
Frequently asked questions
Does a CISA KEV entry prove my system was hacked?
No. It confirms that CISA has evidence the vulnerability has been exploited somewhere. Exposure and compromise still have to be established for your environment.
Is the GitHub Kimi K3 incident still active?
No at this cutoff. GitHub marked the incident resolved, but users should check the live status page for any later incident.
Was every Baylor Genetics data field exposed for every person?
No such claim is supported. Baylor says the affected information varied by person.
Are Epic’s games free permanently?
The claim window is temporary, but a successfully completed $0 base-game claim is added to that Epic account rather than provided as a weekend-only trial.
Sources checked for this edition
- CISA — Known Exploited Vulnerabilities catalog JSON
- GitHub Status — Kimi K3 degraded performance incident
- Baylor Genetics — Security Update
- Hearst Television / WPBF — Baylor Genetics medical-data breach report
- Federal Trade Commission — Credit Freezes and Fraud Alerts
- Epic Games Store — U.S. free-games promotions feed
- Epic Games Store — Breathedge
- Epic Games Store — Rival Stars Horse Racing: Desktop Edition
Sources were reopened during drafting and are rechecked immediately before publication. Automated access limitations are recorded in the private source ledger rather than hidden.