❌

Normal view

Microsoft Patches 1,259 Flaws, Including Exploited Outlook Bug That May Expose NTLMv2 Hashes

11 November 2026 at 08:17
Microsoft on Tuesday released patches for a total of 1,259 vulnerabilities spanning its software portfolio, the second consecutive month where the patch volume has exceeded 1,000 flaws. These cover 726 flaws in Windows, 174 in Office, 61 in Developer Tools, 59 in SQL Server, 53 in Developer Tools, and 27 in SharePoint Server. The patches also include 165 non-Microsoft-issued CVE identifiers.

Railway Says Stolen Customer AI Keys Led to $740,000 in Estimated Unauthorized Usage Charges

11 November 2026 at 07:49
AI provider keys that customers stored on Railway were stolen in an October breach and used to commit an estimated $740,000 in unauthorized spending, the platform-as-a-service provider said yesterday. It has promised to pay those charges itself when an AI provider will not refund them. The company builds and runs apps for its customers and stores their secrets, such as API keys and database

Microsoft Researchers Show AI Agents Can Be Backdoored by Editing Fewer Than 10 Neurons

11 November 2026 at 07:21
An AI model can be given a hidden backdoor by editing fewer than 10 of its rarely used neurons, without retraining the model, Microsoft researchers have shown. When a chosen trigger appears, the model outputs an attacker's command, which an agent using that model would run with the agent's own permissions. The attacker must be able to change the model's weights. The team tested the method on

Cisco BroadWorks and Openwave Flaws Actively Exploited Despite Available Patches

11 November 2026 at 06:04
The U.S. Cybersecurity and Infrastructure Security Agency (CISA) Tuesday added two security flaws impacting Cisco BroadWorks and Openwave Messaging Webtop Media Transcoder to its Known Exploited Vulnerabilities (KEV) catalog, citing evidence of active exploitation. Details of the vulnerabilities are below - CVE-2026-20320 (CVSS score: 7.5) - An improper restriction of XML external entity

OpenAI builds a kill switch for its research models

11 November 2026 at 05:20
In 2019, OpenAI decided not to publicly release a new model because its research uncovered “concerns about malicious applications of the technology.” And on Tuesday, the company announced it has built a kill switch for the models deployed in its research labs, months after some of them displayed disturbing behavior. “As our models get more powerful and the associated safety and security risks become bigger, it becomes more and more critical that we can detect potential issues, and quickly stop models in their tracks when needed,” OpenAI explains in a Tuesday post. The company named the kill switch “Control Room” and described it as “a central system to track model workloads across our research infrastructure and stop them quickly when safety or security concerns arise.” The facility can apparently stop models from producing any output 35 seconds after a decision to pull the plug – and can go faster. “The 35-second lag comes from a caching layer for inference authorization, to support the required volume of traffic. We are working to drive this number down to zero so that we can end jobs instantly,” the company promises. A rookie mistake in critical infrastructure design is to build both production and resilience tools on shared resources that could be taken offline by a single incident. OpenAI seems conscious of that risk, because it says the tool “has been built to keep working even when other systems fail, and to stop model output if Control Room itself goes down.” OpenAI hasn’t explained why it took so long to build a kill switch or why it decided now is the moment when it needs one. The Register fancies recent examples of agents exceeding their brief in worrying ways – like attacking Hugging Face, causing trouble at the Wikimedia Foundation, or going a little too deep when researching Australian healthcare data – may have influenced the timing of this development. “Control Room is already deployed across our research infrastructure, where the need is greatest,” the company’s announcement states. “Our external model-serving stack is already much more centralized by nature, with a well-developed operational capability to quickly take down model deployments if needed.” OpenAI says it plans to “strengthen and expand the system over the coming months, alongside our investments in monitoring for misaligned behavior and security breaches.” That’s a variant of Big Tech’s usual “We’re sorry and we promise to do better in future” proclamation that follows the latest SNAFU. Yet back in 2019, OpenAI pulled the pin before matters ever reached that state. ®

Amplifon Data Breach Reportedly Affects 1.3 Million: How to Protect Your Personal Data

10 November 2026 at 22:57

Amplifon Americas, a U.S. hearing care provider, has disclosed a data breach that affects 1,332,826 people nationwide, according to a Texas Attorney General filing as summarized by BreachTally on Nov. 6, 2026.

Amplifon’s security incident notice says the exposed data includes names, dates of birth, government ID numbers, and health and insurance information, and that Social Security numbers or financial information were affected for a limited number of individuals. Amplifon has not publicly confirmed the total, and the company says it is not aware of any fraudulent use of the information.

How the Amplifon Data Breach Happened

An unauthorized third party obtained files from Amplifon’s systems between Jan. 18 and Feb. 8, 2026, according to the company’s notice. Amplifon says it detected suspicious activity on Feb. 11, 2026, notified law enforcement, and disabled impacted accounts.

The notice says a review of the affected data indicated on Oct. 6, 2026 that certain personal information may have been impacted. That is nearly eight months after detection, and the notice does not explain the timeline. Amplifon says it will notify people for whom it has a valid mailing address, and its Texas filing lists U.S. Mail and a website posting as the methods of notice.

Amplifon has not said how the attackers got in. As of Nov. 9, The Record reported that no hacking group had claimed responsibility. Amplifon also filed notices with state officials, including in Texas and Vermont. The Texas Attorney General’s breach report listing, published Nov. 6, 2026, shows 85,804 Texans affected.

What Information Was Exposed in the Amplifon Data Breach

What was exposed varies by person, and your notice letter lists which of your information was involved. Amplifon’s notice names these categories:

  • Names and contact information
  • Dates of birth
  • Driver’s license, state ID, or other government-issued ID numbers
  • Hearing or medical information, including medical record numbers, dates of service, and other health information
  • Health insurance ID numbers and related information

According to Amplifon, Social Security numbers or financial information “may also have been impacted” for “a limited number of individuals.” The Vermont Attorney General’s breach notice listing for Amplifon names Social Security numbers and health records, and the Texas listing includes Social Security number information among the types affected.

What Can Someone Do With Your Social Security Number?

Criminals can use a Social Security number to try to open new credit accounts in your name, which a credit freeze blocks, or to file a tax return in your name, which the IRS Identity Protection PIN is designed to prevent. Health insurance and medical record details add a separate risk: medical identity theft, which happens when someone uses another person’s information to obtain medical care.

Amplifon says it is not aware of fraudulent use so far. The steps below apply whether or not any misuse has shown up.

What Should You Do If You Got an Amplifon Data Breach Notice?

Read the notice closely, confirm it is genuine, and note which of your information it says was involved. Amplifon’s Texas filing shows that notice was provided by U.S. Mail and a website posting, and the company’s notice says it will notify people for whom it has a valid mailing address.

  • Check that the toll-free number on the letter matches (844) 971-8634, the number on Amplifon’s official notice page. Do not reply to unsolicited calls, texts, or emails about the breach.
  • Note which categories of information the letter lists, especially Social Security number, financial, and medical information.
  • Keep the letter and envelope, with the date you received them.
  • If the letter offers credit monitoring, enroll through the instructions in the letter, not through links in unsolicited texts or emails.

If you used Amplifon hearing care services and did not get a letter, call the hotline on the notice page to ask whether your information was involved. The notice says Amplifon will notify people with a valid mailing address, so a missing letter does not by itself show that your information was not involved. The steps below apply either way.

Warning Signs That Your Information Is Being Misused

Signs of misuse tend to appear in your credit reports, your medical and insurance statements, and the messages you receive.

Warning Sign Why It Matters
An Explanation of Benefits for care you did not receive The FTC lists this as a warning sign of medical identity theft.
A medical debt collection notice you do not recognize The FTC advises checking credit reports for unfamiliar medical collections after a medical identity theft.
Accounts or credit inquiries you did not open Someone may be using your identity details to seek new credit.
A call, text, or email about the breach that asks for your SSN, payment, or login details Messages about a breach can be copied by scammers. Use the phone number on your letter or on Amplifon’s official notice page instead.

How to Protect Yourself After the Amplifon Data Breach

Start by confirming what was exposed, then block new credit in your name and watch your accounts and statements.

  1. Read your notice letter and use official contact details. Note which categories of information it lists. Do not reply to unsolicited calls, texts, or emails about the breach. Contact Amplifon only at the number on your letter or the toll-free line, (844) 971-8634, on its official notice page.
  2. Enroll in the credit monitoring Amplifon offers, if your letter includes it. Amplifon says it is offering 24 months of free credit monitoring and identity protection services to certain individuals, including those whose SSN or financial information was affected.
  3. Freeze your credit at all three bureaus. A freeze blocks new credit accounts in your name. Details are in the next subsection.
  4. Request an IRS Identity Protection PIN. The IRS says this six-digit number prevents someone from filing a tax return with your SSN.
  5. Review statements and credit reports. Look for Explanations of Benefits for care you did not receive, and request your credit reports at AnnualCreditReport.com to check for accounts you do not recognize.
  6. Ask why a provider needs your SSN. McAfee’s guide to safeguarding your family against a medical data breach advises not to hand over an SSN automatically, even when a medical provider asks for it.

Should You Freeze Your Credit After the Amplifon Breach?

Yes, if your notice says your SSN or financial information was involved. The FTC says there is no cost to place or lift a freeze, and that while one is in place nobody can open a new credit account in your name, including you. A freeze does not close existing accounts.

Place the freeze separately at Equifax, Experian, and TransUnion. A free fraud alert, which lasts one year, is a lighter option, but unlike a freeze it does not block lenders from viewing your report.

What to Do If Your SSN or Medical Information Was Misused

If your notice says your SSN was involved, or you see signs of misuse, freeze your credit first, then work through these steps.

  1. Report identity theft at IdentityTheft.gov. The FTC directs people there to create a personal recovery plan, and the Social Security Administration says to report a stolen SSN to the FTC if you believe your identity was misused.
  2. Contact your bank or card issuer if your notice says financial information was involved, and ask about stopping or reversing charges you do not recognize.
  3. Dispute errors. If statements show care you did not receive, request records from each provider, insurer, and pharmacy involved and report errors in writing. The FTC says providers must respond within 30 days. Dispute unfamiliar accounts and medical collections with the credit bureaus.
  4. Keep records. Save your notice letter, call dates, reference numbers, and copies of anything you send.

McAfee’s identity theft recovery guide covers additional steps.

How to Report the Amplifon Data Breach and Related Fraud

  • FTC: Report scams at ReportFraud.ftc.gov and identity theft at IdentityTheft.gov.
  • FBI Internet Crime Complaint Center: Report phishing messages or other internet-enabled fraud at ic3.gov.
  • Local police: File a report if you lost money or someone used your identity.
  • Amplifon: Call the toll-free line on your notice letter with questions about your notice.

Amplifon disclosed the breach in early November 2026, and more details may emerge as the company and regulators release information. Whatever your letter says, the most important protective step is a credit freeze at Equifax, Experian, and TransUnion, because it blocks new accounts opened with exposed identity details.

FAQ

Was Amplifon hit by a data breach, and how many people were affected?

Yes. Amplifon says an unauthorized third party obtained files from its systems between Jan. 18 and Feb. 8, 2026, and that it detected suspicious activity on Feb. 11. BreachTally’s summary of the Texas filing lists 1,332,826 affected people nationwide, a total Amplifon has not publicly confirmed. The Texas Attorney General’s listing shows 85,804 Texans affected.

What information was exposed in the Amplifon data breach?

Amplifon’s notice lists names, contact information, dates of birth, driver’s license and other government ID numbers, health and medical information, and health insurance information. Social Security numbers or financial information were affected for a limited number of individuals, according to the company.

Why did it take Amplifon months to notify people?

Amplifon has not publicly explained the timeline. Its notice says a review of the affected data indicated on Oct. 6, 2026 that certain information may have been impacted, nearly eight months after the Feb. 11 detection.

Does Amplifon offer free credit monitoring, and should I still freeze my credit?

Amplifon says it is offering 24 months of free credit monitoring and identity protection services to certain individuals, including those whose SSN or financial information was affected. Monitoring and a freeze do different jobs: monitoring alerts you to activity, while a freeze blocks new accounts from being opened in your name.

The post Amplifon Data Breach Reportedly Affects 1.3 Million: How to Protect Your Personal Data appeared first on McAfee Blog.

November Patch Tuesday boasts over 1,000 bugs, one already under attack

10 November 2026 at 22:37
It’s another doozy of a Patch Tuesday, with Microsoft fixing 1,094 bugs in its products, including one that attackers exploited before Redmond released a patch. Jake Knott, head of threat intelligence at exposure management firm watchTowr, succinctly said in an email to The Register: “Maybe we should just go home.” “Most security teams haven’t quite recovered from the last month of bumper-to-bumper critical vulnerabilities, emergency patches, and ‘2shell’-branded everything, and we’re yet again at another Patch Tuesday,” Knott told us. Starting with the zero-day: It’s an Outlook spoofing vulnerability, tracked as CVE-2026-124194, and it only garnered a 6.5 out of 10 CVSS rating. But as Dustin Childs, head of threat awareness at TrendAI’s Zero Day Initiative, warns, don’t let the score or the name lull you into thinking it’s OK to put off patching this one. “It’s labeled spoofing, but the impact is bigger than the name suggests,” Childs said in his monthly Patch Tuesday review. “An attacker sends a specially crafted message file and convinces a user to open it,” he wrote. “Outlook then connects to an attacker-controlled network location without showing the usual external-content warning, which discloses the user’s NTLMv2 hash. The attacker can use that hash to authenticate as the user.” Microsoft marked CVE-2026-124194 as exploited, but per usual didn’t say when the attacks started, who is battering this bug, and what they are doing with the access post exploitation. These details will likely start trickling out soon. Plus, now that there’s a public fix, other miscreants are undoubtedly already scanning for vulnerable versions and reverse engineering the patch for their own attack purposes. So prioritize this fix, and keep an eye on your inbox for any suspicious files. Back-to-back months of 1K+ CVEs Despite the second month of more than 1,000 CVEs (October had 1,474), CVE-2026-124194 is the only one under active exploitation, and none of the 1,094 are listed as publicly known. Childs says this shouldn’t give organizations “false comfort.” “Logging back-to-back months above 1,000 CVEs proves automated bug-hunting has permanently reset patch volume,” he told The Register. “With AI making patch-diffing and exploit generation near-instant, the threat window opens the minute these updates drop.” For defenders, this means two things, Childs added. “What defenders need to know and do right now is abandon broad triage and take immediate defensive action: patch Exchange and Domain Controllers (LDAP/Kerberos) first to stop zero-click compromise, ring-fence exposed network services like DNS and DHCP to prevent wormable spread, and verify manual administrative fixes on your cloud services,” he said. Zero-click threats There are two zero-click threats in this month’s batch of fixes: CVE-2026-116928 and CVE-2026-119958. Both are critical, carrying 9.8 CVSS ratings, in part because they don’t require any user interaction to exploit. CVE-2026-116928 is an out-of-bounds write in Microsoft Windows Search Component that could lead to remote code execution. An unauthenticated attacker could abuse this search feature in Exchange “by sending an email containing a specially crafted attachment,” Redmond warned. “Exchange automatically processes the attachment for indexing, so the recipient does not need to open the email or attachment. Successful exploitation could allow the attacker to execute code with the permissions of the affected processing service.” CVE-2026-119958 is an out-of-bounds write vulnerability in Windows' implementation of the Lightweight Directory Access Protocol (LDAP) that could allow unauthenticated attackers to execute code remotely without user interaction. This one can be exploited by sending specially crafted LDAP requests to vulnerable systems, potentially compromising domain controllers. Childs also counts 30 CVEs that pose a “wormable risk,” requiring zero authentication and zero user interaction over a network. All of those are listed in his blog, so prioritize fixing those as well. And…Xbox remote code execution And finally, for funsies, a critical flaw in the Windows Xbox Live Networking Service, CVE-2026-112967, that could allow remote code execution also made this month's roundup. It's a heap-overflow vulnerability with a 9.8 CVSS rating that doesn't require authentication or user interaction to exploit. So don't take a gaming break between testing November's updates. Or, if you do, at least make sure vulnerable Windows systems running the Xbox Live Networking Service are on your patching list, too. ®

Microsoft Fixes Nearly 1,100 Security Vulnerabilities

10 November 2026 at 21:55

Microsoft did another four-digit patch drop today, releasing updates to fix almost 1,100 security vulnerabilities in its Windows operating systems and supported software. This month’s Patch Tuesday addresses 63 critical flaws — including a zero-day in Microsoft Outlook — and comes amid important security updates from other software makers, including Adobe, Apple, Google and Mozilla.

Image: Shutterstock.com. Diorama by @zepp1969.

November’s patch release from Redmond tackles 1,093 vulnerabilities, fixing 63 “critical” flaws that can be exploited to seize control over a Windows system with little or no help from users. Nearly half of those critical bugs are remote code execution vulnerabilities. Overall, 535 of the flaws addressed this month allow an attacker to elevate their privileges on a vulnerable device.

This latest round of updates means Microsoft has shipped more than 5,100 security patches so far this year, a staggering number considering that a year ago Microsoft was averaging around 100 patches per month. Microsoft credits advances in artificial intelligence for helping to find (and fix) such a large volume of security bugs in recent months. Last month, Microsoft pushed more than 1,400 fixes.

According to Redmond, just one of the flaws is already seeing active exploitation: CVE-2026-124194, a spoofing bug in Outlook. The advisory for CVE-2026-124194 says it affects Microsoft 365 Apps for Enterprise and editions of Microsoft Office.

Several other major software makers pushed security updates this week to fix critical weaknesses in their products. Apple on Monday released out-of-cycle security updates to fix at least nine vulnerabilities in iOS/iPadOS, macOS, watchOS and visionOS. Among the weaknesses reportedly fixed in Apple’s release include an iMessage flaw that could let a remote attacker join a group chat and receive its messages; the updates also fix a separate iMessage flaw that could let someone added to a group access messages sent before they joined.

Lee Neely, an instructor at the SANS Institute, noted that Apple backported the fix to iOS 18.

“I take notice when Apple releases fixes to more than two versions,” Neely wrote in a SANS newsletter today. “You really need to get to version 27.2.1 of their OSes and push folks who are holding onto devices which cannot run the current version. The best plan often involves setting an upgrade date for old hardware. Run through all your Apple devices and make sure everything is up to date, don’t assume the fixes went out automatically.”

Google this week released Chrome version 157.0.8103.50, which resolves nine security holes, including CVE-2026-125350, the sixth zero-day vulnerability this year for Chrome (this bug also is being patched in Chromium-based browsers like Edge). The latest Chrome version follows its November 3 release, which fixed 213 vulnerabilities. A new version of Mozilla Firefox out today (Firefox 160) resolves almost 100 CVEs, about half of them high severity.

Adobe today released patches for at least 110 vulnerabilities across a range of products, with nearly half of the flaws rated high severity. Adobe said there is no evidence any of the security holes it addressed this month are being actively exploited.

Chris Goettl, vice president of product management at Ivanti, said it’s easy for security teams at large enterprises to feel overwhelmed by the volume and criticality of patches from Microsoft lately. But he notes that while some 95,000 vulnerabilities have been assigned CVEs this year across all vendors, only 217 have so far this year been added to the Known Exploited Vulnerabilities (KEV) list maintained by the U.S. Cybersecurity and Infrastructure Security Agency (CISA).

“Roughly four in ten of this year’s exploited vulnerabilities sit in operating systems, endpoint software, browsers, and server platforms, which a continuous patch strategy can close quickly,” Goettl said.”The rest calls for exposure management alongside patching, especially the 44% that sit in edge devices and IT management or remote access tools, the internet-facing systems that hold privileged access. Teams that can quickly identify those assets, confirm exposure and act on confirmed exploitation can focus on the small slice of vulnerabilities attackers are actively using, while the rest stays on the normal patch cadence.”

Please don’t neglect to back up any important data if you haven’t recently; generally speaking, this is a task best accomplished before applying operating system updates. As ever, if you experience any issues installing this month’s bundle of love from Microsoft, please drop a comment about it in the space below.

Ring robots ready to patrol paranoids’ pads

10 November 2026 at 21:45
If you didn't have any privacy concerns about slapping a Ring doorbell on your front door or putting Ring cameras inside, you'll love Amazon's newest offerings, which move around homes and businesses to capture views stationary cameras might miss. The house of Bezos announced the launch of Ring Robotics on Tuesday along with its first two products: a drone designed for indoor home security, and a wheeled robot with a telescoping camera mast for automated after-hours business patrols. Both are designed to proactively patrol spaces as well as respond to alerts from connected alarm systems and Ring-connected devices. According to Ring founder Jamie Siminoff, this is something customers actually want, as those stationary cameras just can’t quite see everywhere. “It’s not just a new category of security; it’s the beginning of a future where proactive, autonomous protection is something every home and every business can have,” Siminoff said. The consumer-focused Ring Drone Cam launches from its own charging dock that Amazon says keeps the thing “out of sight” when not in use, and when in flight is able to patrol a home by flying around pre-programmed routes to take in the sights with its 148-degree FOV, 2K camera that includes LED illumination for night patrols. Amazon says it can also respond to alerts from cameras, sensors, and alarm systems. The Ring Rover Cam, designed with businesses in mind, is sort of like a security Roomba that sports a camera on a telescoping mast that Amazon says can be programmed to certain heights to let it see over counters, shelves, and other workplace obstacles. The Rover can also perform 360-degree scans and includes a siren, lights, and two-way audio so you can yell at intruders who aren't dissuaded by its presence. The Rover streams and records video in up to 4K while moving or patrolling and is designed to make regular patrols of businesses during off hours. It can also detect people and respond to alerts from connected Ring devices. Of course, given that this is Ring we're talking about, these flying and free-wheeling cameras use Amazon's cloud for some processing, likely inviting privacy concerns about what footage and mapping data the company can access and retain. The Amazon-owned security tech firm has faced a number of privacy complaints over the years, some of which have resulted in multimillion-dollar settlements. Ring agreed to pay $5.8 million in a 2023 settlement with the FTC over allegations that employees and contractors improperly accessed customers' private videos and that the company failed to adequately protect accounts against unauthorized access – just imagine the privacy concerns raised by flying robots. More recently, the company took heat for partnering with surveillance outfit Flock Safety, a relationship which it has since canceled. Amazon/Ring also invited criticism for a Super Bowl ad earlier this year promoting a new feature called Search Party, which would remotely activate Ring cameras to search for lost pets, suggesting that Amazon had the ability, in theory, to use Ring cameras like a dystopian neighborhood surveillance network. Another Ring feature, Familiar Faces, which uses AI-powered facial recognition to identify people captured by compatible cameras, prompted a proposed class-action lawsuit filed in June. The complaint alleges that the feature collected biometric information from visitors and passersby without their consent. If we can’t have iRobot, we’ll do it with Ring Amazon abandoned its efforts to buy Roomba robot-vacuum maker iRobot in 2024, blaming regulatory scrutiny for the move. The FTC, under then-chair Lina Khan, examined the deal's potential effects on competition and consumer privacy, including concerns about the information Roombas collect while mapping customers' homes. European regulators, meanwhile, raised concerns that Amazon could use its marketplace to disadvantage rival robot vacuum makers. With this Ring move, Amazon is once again putting robots capable of mapping interior spaces into customers' hands, reviving some of the privacy questions raised during its failed iRobot acquisition. As Amazon explains in Tuesday’s press release, both new Ring robots are powered by AI Pilot, “a custom-built system that uses the devices’ cameras, specialized vision models, on-device sensors, and cloud processing to see, think, and navigate autonomously.” To help the Ring robots understand where they're operating, the devices generate floor plans of interior spaces, according to Amazon. “Carry Ring Drone through your space or let Ring Rover autonomously explore, and it turns what it sees into a floor plan,” the company explains of the setup process. AI Pilot takes the reins in identifying the types of rooms it sees and suggests key patrol areas it should focus on, which users can add to in the Ring app. Amazon claims that videos captured by these new flying and free-wheeling cameras will be protected by an encryption scheme it calls Throw Away the Key Encryption (TAKE). The system temporarily allows Ring's cloud services to access recordings for enabled features before the relevant encryption keys are deleted. Ring announced the scheme in August, presenting it as a way to limit access to customer recordings without sacrificing cloud-powered features. “With TAKE, your Ring videos are protected with unique, rotating encryption keys,” Amazon explained. “A copy of the keys is temporarily held inside a secure enclave within the cloud; think of it as a sealed vault that can only provide Ring access to the key under strict, limited conditions.” The keys, Amazon claims, are later deleted so that only users and those they allow access to can see videos, with Ring only retaining them “to power the intelligent features that you have active on your account.” “We take privacy concerns seriously, and we believe privacy and customer control are fundamental to building products people trust,” a Ring spokesperson told The Register when asked about prior privacy concerns. “That is why customers decide where these devices go and when.” We asked about floor plan security, but didn’t get an answer about that. As for when those devices will be available, the Rover Cam will start shipping on December 16 at a price of about $1,000, but the Drone Cam might not ever actually make it to homes. Amazon’s announcement mentions a release date of January 27, 2027, but that’s subject to the FCC giving its blessing. “Ring Drone Cam has not been authorized as required by the rules of the FCC,” Amazon’s release states. “This device is not, and may not be, offered for sale or lease, or sold or leased, until authorization is obtained.” Amazon told us that the Drone Cam would still start shipping in January, luckily giving everyone a few months to figure out how to deal with this new, more mobile, invasion of privacy. ®

Finally, Payment by Bank Transfer Comes to Have I Been Pwned

10 November 2026 at 20:26
Finally, Payment by Bank Transfer Comes to Have I Been Pwned

This is simultaneously the most boring yet exciting blog title I've written in a long time. How you pay for services isn't exactly a sexy topic, but it solves a problem that's been a massive bugbear for a long time.

Here's a brief history of the issue: many organisations have policies that make it extremely hard to purchase goods and services with a credit card. I wrote about this more than two years ago now, where I referred to "Neville" in the procurement department who, because "reasons", demanded an invoice in advance and payment via electronic funds transfer (EFT) only. That ultimately means the world's most popular way to make online payments is out of reach for them. Unfortunately, until today, that was the only way we could take payment via Stripe, which processes all our online HIBP purchases. That left only two options for orgs in this situation:

  1. Don't use Have I Been Pwned at all 😢
  2. Buy a subscription via a reseller 🤢

The problem with the first option is obvious. The second option "solved" the first problem by allowing a company to pay a reseller by EFT, who then paid us by card. The reseller would then mark the price up (often significantly), slow the whole process down, log countless tickets with us (despite the existence of a dedicated portal for them), and frankly, just be a pain in the arse for everyone. It's hard to express the level of disdain I have for most resellers, and I even still have a 1,381-word draft blog post titled "That's it - Resellers are now Banned from Have I Been Pwned", which I held back from posting. Why? Because I've walked in the shoes of the folks trying to purchase our services who are just trying to get their job done, and Neville has told them they can't pay by card. That was me in a previous life, and it sucked. We kept resellers solely to support those people.

But today, HIBP's subscription page has something all new on it:

Finally, Payment by Bank Transfer Comes to Have I Been Pwned

Stripe has given us early access to EFT payments in Australia. They've been available in the US for a while, but as an Aussie company and with global financial systems being what they are (i.e. not always the most flexible), we just didn't have that option. Until now. So, we've added EFT as a payment method to our Pro and High RPM plans and kept the entry-level Core ones on card only, as there's some additional overhead on our end. You'll see these every time you go to purchase an eligible subscription:

Finally, Payment by Bank Transfer Comes to Have I Been Pwned

When you choose to pay by bank transfer, you're given a form for your company details (this is how we calculate any applicable taxes), then a Stripe payment link which loads something similar to the following:

Finally, Payment by Bank Transfer Comes to Have I Been Pwned

The first thing is that, being an Aussie company with an Aussie bank account, we need to reflect EFT payments in AUD rather than USD. It makes sense when you think about it: we do USD for all the existing products paid for by card, and whatever the FX conversion gods decide is the corresponding Aussie amount eventually lands on our end. But that's a model where the card is charged, and access is granted immediately. For EFT, funds flow through the wires, do FX conversion for non-Aussie purchasers, land in the target account and then Stripe webhook magic enables the service. We need that exact amount to land on our end, so we can't be rolling the dice on what exchange rate we're going to get; hence, Stripe requires us to charge in the target currency. The products are exactly the same price based on the rate we currently see via Stripe purchases today (about 69 American cents per Aussie dollar), we'll just have to see if that's revised in the future with any major currency fluctuations.

Next are the banking details. Pretty straightforward, and I'm sure we've all made payments to an account like this before. The main thing is that the account number is a virtual one, which is how Stripe reconciles money that comes in from a previously raised invoice. When you sell a very limited number of products and a bunch of customers are buying the same one, this is how Stripe is then able to reconcile who has paid for what. If you really want to geek out on bank payments, Stripe has a dedicated EFT explainer page.

And finally, subscriptions in HIBP begin as soon as the invoice is raised, but access to the service only begins when payment is made. You can see the problem if we didn't do it this way: bad guy spins up the service and immediately starts using it then just never pays. But this all ties into the quote ecosystem in the existing HIBP dashboard, so it's easy to generate a quote, go flick it to Neville, get it approved, then raise and pay the invoice straight away.

As I said in the opening, it's not the most exciting topic, but it's a major thing for us and the customers who were left with only bad options if they genuinely couldn't pay by card. In the aforementioned draft blog post on binning resellers, I'd written about how we'd seen markups of up to 131% (so yes, more than double the price!), with absolutely zero value add (i.e. they don't do any product support, that remains entirely on us). But the burden resellers really put on us is the support they require to make purchases; in that same draft post, I calculated that resellers accounted for 0.86% of all sales but 43% of all support tickets. That's just nuts, especially for such a small team (although Bruce has helped enormously).

We hope this makes life easier for a bunch of people who were previously stuck between a rock and a hard place, and that includes all the "Nevilles" out there too. This is all now live and accessible via the pricing page. If you run into any issues, Bruce is standing by in the support portal.

Cracking Server 2022 NTLMv1-SSP Hashes with Rainbow Tables

A while back, I had released a blog showing that NTLMv1 downgrade attacks still work on Windows Server 2022! While it isn't a default setting, it's still a misconfiguration to potentially look for.

If a DC’s LmCompatibilityLevel is set to 0-2, you can coerce authentication, strip Extended Session Security (ESS), and obtain an NTLMv1-SSP hash that’s crackable with a rainbow table. :)

Blog: https://hunio.org/security/ntlmv1-ssp-cracking/

submitted by /u/elohhs
[link] [comments]

Git Patches Flaw That Lets Malicious Repositories Execute Code During Recursive Clones

10 November 2026 at 19:23
A flaw in Git can let a malicious repository run an attacker's code on a computer that clones it recursively, together with its submodules. The Git project fixed it this week in Git 2.56.1, with matching fixes for the 2.50 through 2.55 series in 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1 and 2.55.1. The flaw, tracked as CVE-2026-111760, is an integer truncation in how Git handles its index. An

SGLang RCE Exploit Breaches NEAR AI, Steals Data From 18 Agents and About 100 Users

10 November 2026 at 19:19
An attacker exploited a remote code execution flaw in SGLang, an open-source inference engine, and ran code on one of NEAR AI's inference servers last Sunday. The attacker could also have seen requests being processed on that server that day, including requests sent in confidential mode, the company said earlier this week. That mode processes requests inside a trusted execution environment (TEE

Barracuda’s email security gateways bitten by make-me-root vulns

10 November 2026 at 18:51
Security company Barracuda warns that attackers are exploiting a pre-authentication authorization bypass bug and a command-injection vulnerability in its popular Email Security Gateway (ESG) products that, when chained, could allow the crims to run commands with root privileges. “We have identified exploitation activity affecting a small number of organizations,” the security vendor said in a late Monday night update to its earlier security advisory. Barracuda declined to answer The Register’s questions, including one about how many organizations have been hit by attackers. A company spokesperson told us that it “worked directly” with the affected businesses “to quickly address the issue. Barracuda acted promptly to remediate the vulnerabilities, releasing patches for affected products.” The vendor disclosed and fixed the vulnerabilities, CVE-2026-116606 and CVE-2026-111560, last week. CVE-2026-116606 is a 9.3 CVSS-rated, pre-authentication authorization bypass flaw in ESG. While authentication is not required to exploit this vulnerability, the attacker must have access to the administrative user interface. As Purplecop Security founder Tausif Ahmed said on Tuesday: “If your Email Security Gateway's admin UI is open to the internet, that's the first thing I'd close today.” CVE-2026-111560 is an 8.6-rated command-injection flaw that affects multiple Barracuda products: its ESG, load balancer (ADC), message archiver (BMA), web application firewall (WAF), WAF control center (WCC), and web security gateway (WSG). “If exploited in combination, these vulnerabilities could allow an attacker to bypass authorization controls and obtain root access to the device,” Barracuda warned on November 2. At the time, the vendor did not report any active exploitation of either. We don’t yet know who is responsible for the attacks, or whether the intruders gained root access – but if they did, they could steal data, install backdoors, and take full control of affected systems. These types of edge-device exploits have been used by Chinese-government spies, and in 2023 the FBI blamed PRC-linked attackers for a series of attacks that targeted Barracuda ESGs to deploy custom malware and maintain access to high-value networks. According to Mandiant, 27 percent of identified affected organizations were government entities. So if you haven’t already: patch now. ®

Hackers Exploit Critical Xen Orchestra Auth Bypass Flaw to Gain Admin Access

10 November 2026 at 18:12
French software company Vates VMS has warned of a critical security vulnerability in Xen Orchestra that it said is being actively exploited in the wild. The authentication bypass flaw, which does not yet have a CVE identifier, is tracked as VSA-2026-062. "REST cookie parsing turns authenticationToken=j:%7B%7D into {}," Vates VMS said in an alert. "REST authentication passes that object to the

Three China-Nexus Espionage Campaigns Linked Through Sparrow Malware Ecosystem

10 November 2026 at 17:43
Three distinct threat activity clusters with shared infrastructure and malware code similarities have been observed targeting telecommunications providers, government organizations, military entities, research institutions, and critical infrastructure across Latin America, Asia, and Europe over the past year. Check Point Research is tracking the clusters under the names SilentDelivery,

❌