Apple to Pay $250 Per iPhone Duo Foldable Display in Samsung Deal
Samsung Display has signed a three-year exclusive supply agreement with Apple to provide foldable display panels for the iPhone Duo and future models, reports Chinese leaker Instant Digital. The iPhone Duo is the first device on the market to feature Samsung's M16 OLED material set, said to bring improvements to brightness, color performance, lifespan, and power efficiency over previous OLED generations. Apple will reportedly pay around $250 per panel, making it one of the device's priciest components.Related Roundup: iPhone DuoTags: Foldable iPhone, Instant Digital, SamsungBuyer's Guide: iPhone Duo (Coming Soon)Related Forum: iPhoneThis article, "" first appeared on MacRumors.comDiscuss this article in our forums

Read more »

Apple Explains What Happens to Conversations Siri Recap Hears
The Apple Watch Series 12 and Ultra 4 have new Audio Intelligence features that include Sound Recognition, Music Recognition, Live Rewind, and Siri Recap. When these features are activated, the new Apple Watches are always listening to what's going on around the wearer. With ‌Siri‌ Recap, the Apple Watch listens to your conversations throughout the day and takes notes. It uses Apple Intelligence to continually generate summaries that Apple says are meant to "jog your memory" on events so you can stay present in the moment. Apple anticipated negative reactions to a wearable that's always listening, so it has a detailed explainer on the privacy features that have been added. No speaker attribution - ‌Siri‌ Recap will not identify and attribute speakers. Names can be included if mentioned in the conversation, but nothing is directly attributed to a specific person. Omitted information - ‌Siri‌ Recaps will omit potentially harmful content or sensitive data, which Apple says includes language that promotes self-harm or hateful speech, financial data, government-assigned identifiers, authentication data, and certain personal identifiers. Caveats - Apple warns that ‌Siri‌ Recap summaries can be incomplete or inaccurate, and filtering may not remove all sensitive information. No transcript - Apple says ‌Siri‌ Recap doesn't produce a full transcript of a conversation. It's just a summary, comparable to notes one might jot down after a conversation. Condensed conversations - Encrypted, condensed text versions of a conversation are sent to Private Cloud Compute. The text is less than half the length of the original transcript, and distills the conversation to its core meaning. Conversation tone, non-essential language, filler words, and redundancies are removed. No audio recording - Audio is sent to the Secure Exclave on Apple Watch and iPhone for processing and analysis. It can't be accessed by the operating system, apps, the user, or Apple, and no audio is recorded or stored. Private Cloud Compute - ‌Siri‌ Recap uses Apple Foundation Models running on Private Cloud Compute to summarize and format the final output. Data is not accessible to Apple or anyone else. Opt in, not opt out - ‌Siri‌ Recap can be turned on in the Apple Watch app on iPhone, and set to listen on a schedule. You can have it on only at work, or set it to never listen at night. There will be a quick access toggle in Control Center for turning it on and off. Auto-delete - Summaries auto-delete after seven days if not saved to the ‌Siri‌ app. Siri app - Summaries are saved to the ‌Siri‌ app and can be deleted at any time from all synced devices. Saved summaries can be exported to other apps like Notes. Encryption - Summaries are end-to-end encrypted when synced to your other devices via iCloud so only your trusted devices can access them. Apple suggests that Apple Watch wearers "be mindful" of the people around them. "While audio is not recorded and stored, and no speakers are attributed, consider those around you where conversations might be private or sensitive," reads Apple's document. ‌Siri‌ Recap requires one of the new Apple Watch models and an iPhone 16 or later (except the iPhone 16e). The feature is launching later this year.Related Roundup: Apple Watch 12Tag: SiriBuyer's Guide: Apple Watch (Buy Now)Related Forum: Apple WatchThis article, "" first appeared on MacRumors.comDiscuss this article in our forums

Read more »

Apple Watch Ultra 4 Drops GLONASS Support
Apple removed GLONASS support from the Apple Watch Ultra 4, according to technical specifications listed for the device. The Ultra 4 supports GPS, Galileo, QZSS, and BeiDou, while the prior-generation Ultra 3 supported GPS, GLONASS, Galileo, QZSS, and BeiDou. GPS, Galileo, BeiDou, and QZSS use CDMA-based signaling and support multiple frequencies for more accurate positioning. Consumer devices typically only receive an L1 signal from GLONASS, so it is less useful on devices with dual-frequency support. GLONASS also uses a different signal architecture, and receivers have to correct for hardware timing delays on a per-satellite basis, which can lead to positioning errors. Apple did not say why GLONASS support was removed, but dropping it could improve accuracy, reduce processing, and possibly improve battery life. The Apple Watch Series 12 continues to support GLONASS, likely because the L1-only limitation is less relevant on a single-frequency device.Related Roundup: Apple Watch Ultra 4Buyer's Guide: Apple Watch Ultra (Buy Now)Related Forum: Apple WatchThis article, "" first appeared on MacRumors.comDiscuss this article in our forums

Read more »

T-Mobile to Charge $5 a Month for iOS 27 iPhone Handoff
T-Mobile will charge customers $5 per month to use iPhone Handoff, an e-SIM feature that allows the same phone number to be used on two separate iPhones. iPhone Handoff requires carrier support, and at launch, only T-Mobile users in the U.S. and Deutsche Telekom users in Germany will be able to use it. T-Mobile says customers can use their number across two compatible iPhone models and elect which phone is active at any given time. Features like calls, texts, data, mobile hotspot, Scam Shield, and T-Satellite will work on both devices with an eligible plan. Apple is adding support for iPhone Handoff in iOS 27. It requires two iPhones running ‌iOS 27‌ or later that are connected to Wi-Fi and signed into the same Apple Account with FaceTime, iMessage, and Messages in iCloud turned on. It can be turned on when activating a new iPhone or in the Settings app. When iPhone Handoff is enabled, one iPhone serves as a main iPhone and the other iPhone is the secondary device that shares the same number. Moving between the main iPhone and secondary iPhone happens automatically when you unlock one of the devices. A phone number can only be active on one iPhone at a time when using iPhone Handoff. Payment cards in the Wallet app and car keys can work across both iPhones, but Apple warns some Wallet items like transit passes, IDs, or corporate badges might only work on one iPhone at a time. iPhone Handoff also does not transfer an Apple Watch from one iPhone to another. iPhone Handoff works with Dual SIM as long as both eSIMs are from carriers that support iPhone Handoff. Both eSIMs will switch simultaneously when you unlock your iPhone. Each eSIM has to be set up separately. Once set up, iPhone Handoff remains activated until you contact your carrier to turn it off. More information can be found in Apple's support document for the feature. ‌iOS 27‌ is set to launch on Monday, September 14, and the new iPhone 18 Pro models will launch on Friday, September 18.Related Roundups: iOS 27, iPadOS 27Tag: T-MobileRelated Forum: iOS 27This article, "" first appeared on MacRumors.comDiscuss this article in our forums

Read more »

You Can't Use Apple Watch's Live Rewind Secretly, Apple Says
With the Apple Watch Series 12 and Ultra 4, Apple is adding Live Rewind, which relies on an S11 processor and new continual listening features. Live Rewind listens to what's happening around the wearer, and when activated with a double press on the Digital Crown, offers a transcript of what was said in the last 15 seconds. Apple says the feature will let users catch something they missed or are less familiar with. Snippets can be referred to Siri for further evaluation or saved to the ‌Siri‌ app. Apple users are already expressing privacy concerns about Live Rewind, and likening it to Meta's much-maligned smart glasses, but no Apple Watch user will be able to activate it surreptitiously. When the Digital Crown is pressed for Live Rewind, the Apple Watch will sound an audible chime from the speaker. The chime will sound even if the Apple Watch is on silent or if headphones are connected. At the same time, a full-display animation and microphone indicator will appear, with the combination meant to alert those nearby that the feature has been activated. Apple says Live Rewind only activates with a deliberate press on the Digital Crown and all processing is done on-device. It shows the last 15 seconds of speech as a text snippet on the display, and does not continue to transcribe in the background. It can be turned on or off through the Watch app on the iPhone. The Apple Watch Series 12 and Ultra 4 have an S11 chip equipped with a Secure Exclave. Apple describes the Secure Exclave as a hardware-isolated compartment that processes sensor data separately from the rest of the system. Data processed and analyzed in the Secure Exclave is not accessible by the operating system, apps, the user, or Apple. Live Rewind and other Audio Intelligence features do not generate audio recordings. Audio flows into the Secure Exclave, is processed, and then deleted. According to Apple, Live Rewind text snippets "disappear permanently" from the Apple Watch approximately 30 seconds after the Apple Watch display dims, unless the info is saved to the ‌Siri‌ app. Live Rewind requires an Apple Watch Series 12 or Apple Watch Ultra 4 paired with an iPhone 16 or later, though the iPhone 16e is not compatible. Apple Intelligence and ‌Siri‌ AI are required, and the feature is not available for users under 13. The feature will launch later this year and won't be in the initial versions of watchOS 27 and iOS 27.Related Roundup: Apple Watch 12Buyer's Guide: Apple Watch (Buy Now)Related Forum: Apple WatchThis article, "" first appeared on MacRumors.com

Read more »

Ceramic Series 12 is Pricier to Repair Than Apple Watch Ultra 4
Apple reintroduced a ceramic case for the Apple Watch Series 12, but if you don't have AppleCare+, repairs are unusually expensive. It costs $599 to fix "other damage," which covers any repair besides a battery replacement. Battery service is priced at $99. Repairing a ceramic Series 12 is more expensive than getting an Apple Watch Ultra 4 repaired. That repair costs $549 without ‌AppleCare‌+ (up $50 from the prior model). A repair for a cellular aluminum Series 12 of the same size is $349. Apple Watch Series 12 models in the Pearl White or Night Blue ceramic options are priced starting at $899, while the Apple Watch Ultra 4 is priced starting at $799. With ‌AppleCare‌+, Apple Watch users will only need to pay a $69 service fee for damage to the ceramic Apple Watch Series 12 or $79 for the Apple Watch Ultra 4. Battery service is free if a watch's battery capacity drops below 80 percent, and theft or loss has a $119 deductible. ‌AppleCare‌+ with Theft and Loss for the Apple Watch Series 12 is $4.99 per month, and it's $5.99 per month for the Ultra 4. Customers can also opt for ‌AppleCare‌ One, Apple's $19.99 per month option that covers up to three devices. Starting on September 14, Apple is also offering ‌AppleCare‌ One Family, which is $49.99 per month for up to six family members.Related Roundups: Apple Watch 11, Apple Watch Ultra 3Buyer's Guide: Apple Watch (Buy Now), Apple Watch Ultra (Buy Now)Related Forum: Apple WatchThis article, "" first appeared on MacRumors.comDiscuss this article in our forums

Read more »

Mac's Edge Light Feature Rumored to Expand to iPhone
macOS 26.2 added an Edge Light feature to Macs with the M1 chip or newer, and it has now been rumored that this feature will expand to the iPhone. According to pdfu, who has been digging through code in Apple's software updates in recent weeks, the iOS 27 Release Candidate contains evidence of the Edge Light feature coming to the iPhone Duo at a minimum. However, it appears that the feature is still in development, as they said the color temperature setting is not fully implemented. On the Mac, Edge Light illuminates the borders of the screen to evenly illuminate your face in low-light conditions. The feature is essentially a virtual ring light, and there are settings to adjust the width of the white line around the screen and a color temperature slider to make the light it produces appear more or less warm. Edge Light is coming to iPhone.iOS 27 RC gates the feature behind a device subtype that points to iPhone Duo. The color temperature setting isn't fully implemented. pic.twitter.com/dc4pQmikJc— pdfu (@itspdfu) September 10, 2026 Based on a video of the feature in action on a simulated iPhone, it appears that the feature will work in a similar manner and have the same brightness and color temperature settings on the iPhone. It is unclear if Edge Light will be available on the iPhone Duo when the device launches on October 23, or if it will expand to other iPhone models. Some of pdfu's other Apple-related code findings have already proven to be right, so the user has an accurate track record so far.Related Roundups: iOS 27, iPadOS 27, iPhone DuoTag: pdfuRelated Forums: iOS 27, iPhoneThis article, "" first appeared on MacRumors.comDiscuss this article in our forums

Read more »

Apple Rates iPhone 18 Pro Slightly Easier to Repair Than 17 Pro
Apple's repairability scores suggest the iPhone 18 Pro and ‌iPhone 18 Pro‌ Max are slightly easier to repair than the iPhone 17 Pro and ‌iPhone 17 Pro‌ Max. Apple released the repairability data in a product information sheet required by EU energy labeling regulations [PDF]. The EU requires smartphone makers to self-rate repairability across categories like disassembly depth, fasteners, tools, spare parts, software update duration, and repair information. Each category gets a 0–5 score, which is combined into the overall index number. Here are the ‌iPhone 18 Pro‌ and Pro Max scores compared to the ‌iPhone 17 Pro‌ and Pro Max scores. Overall index - 3.14, up 0.10 from 3.04 Disassembly depth - 2.75, up 0.10 from 2.65 Fasteners - 3.80, no change Tools - 2.55, up 0.50 from 2.05 Spare parts - 4.00, no change Software updates - 1.00, no change (EU only awards a higher software core when manufacturers agree to support devices beyond the five-year minimum) Repair info - 5.00, no change It looks like the ‌iPhone 17 Pro‌ models and the ‌iPhone 18 Pro‌ models have similar builds and are repaired in largely the same way, but there are small gains in tools and disassembly depth. Apple may have new tools for accessing some components, but the regulatory filings don't go into specifics. Both devices are class C on the A-E scale that appears on the iPhone's label. We won't have to wait long to see what's changed inside the new iPhone models, because repair site iFixit is likely planning a teardown of one of the new iPhones on or shortly after the September 18 launch date. Since the iPhone Duo isn't available for pre-order yet, Apple hasn't published similar repair data for the device.Related Roundup: iPhone 18 ProRelated Forum: iPhoneThis article, "" first appeared on MacRumors.comDiscuss this article in our forums

Read more »

RIP, iPhone Ultra
For many months, tech blogs like ours used the name iPhone Ultra to refer to Apple's rumored foldable iPhone, but the device ended up being named iPhone Duo. The name iPhone Duo was not a complete surprise. Daring Fireball's John Gruber accurately guessed that the device would be named iPhone Duo all the way back in April, and the name made the rounds again on social media last week. iPhone Ultra became the more common name in rumor coverage after Bloomberg's Mark Gurman floated it as a potentially fitting name for the device back in March, and he later reported that many Apple employees referred to the device as the iPhone Ultra. Plus, former Macworld reporter Filipe Espósito cited a source familiar with Apple's plans who said the foldable iPhone would be named iPhone Ultra. Evidently, that source was wrong. To his credit, Gurman ended up confirming the iPhone Duo name in a last-minute report published shortly before Apple announced the device. Apple avoiding the name iPhone Ultra makes sense, as the device now known as the iPhone Duo is not the most "ultra" version of the iPhone available. Yes, the iPhone Duo has a large 7.6-inch inner display when opened, but on the other hand the device lacks features such as a dedicated Telephoto camera, Face ID, and an Action button. Apple has used Duo branding in the past for its PowerBook Duo line of laptops in the 1990s and the MagSafe Duo Charger in the early 2020s. In the case of the iPhone Duo, the word Duo obviously refers to the device's dual screens. Apple does have some products and services with Ultra branding, including the Apple Watch Ultra, CarPlay Ultra, and the M1 Ultra through M5 Ultra line of chips. And with Apple rumored to be a planning a special 20th-anniversary iPhone, perhaps there will still be an opportunity for the company to use the name iPhone Ultra in the future. For now, though, the iPhone Ultra rumor is dead.Related Roundup: iPhone DuoTag: iPhone UltraRelated Forum: iPhoneThis article, "" first appeared on MacRumors.comDiscuss this article in our forums

Read more »

Upgrading to Apple Watch Series 12 Could Cost You Hypertension Notifications
Some Apple Watch users who upgrade to the Series 12 or the Ultra 4 might temporarily lose access to hypertension notifications. On the watchOS feature availability page, Apple says notifications might not be available on the Series 12 or Ultra 4 at launch because regulatory clearances are in process. Hypertension Notifications may not be available on Apple Watch Series 12 or Ultra 4 in your region, as additional regulatory clearances for these devices are in process. The warning applies to 33 countries and regions, including Canada, Australia, India, Brazil, Singapore, Japan, Taiwan, South Africa, South Korea, and the UAE, with a full list on Apple's website. The Apple Watch Series 12 and Apple Watch Ultra 4 have revamped sensors and a new Health Sensing System. Apple added new optical and electrical heart sensors for more frequent and accurate tracking, and the change appears to require new regulatory approval in some locations. What's new: ECG - The electrodes in the watch cover more surface area for improved skin contact during ECG readings. Optical sensing - Redesigned photodiodes are organized in a ring to capture light more efficiently. Heart rate measurement - Larger, power-efficient green LEDs in the optical heart rate sensor allow the new watches to measure heart rate every five seconds all day, offering more data on a user's fitness and physiological state. Real-time heart rate is available in the updated Heart Rate app, and Exercise and Move Activity rings are more accurate. HRV is also measured as often as every five minutes. Apple Watch users who get these notifications today may lose the option when upgrading to the Series 12 or Ultra 4 until regulatory clearance is granted. Countries not on Apple's list with a footnote will continue to get notifications as usual. This includes the United States, UK, and all EU countries.Related Roundups: Apple Watch 11, watchOS 26, watchOS 27Buyer's Guide: Apple Watch (Buy Now)Related Forum: Apple WatchThis article, "" first appeared on MacRumors.comDiscuss this article in our forums

Read more »

iOS 27 Apple Health App Redesign: Every New Feature Coming in 2026
Apple is planning a major redesign of the Health app on iPhone and iPad, with a long list of new features set to be added. Apple announced the Health app changes at yesterday's iPhone event. The Health app is getting an update because Apple overhauled the sensors in the Apple Watch Series 12 and Apple Watch Ultra 4. There's a Health Sensing System with three main improvements: increased electrode surface area for better skin contact during ECG readings, redesigned photodiodes arranged in a ring to capture light more efficiently for optical sensing, and power-efficient green LEDs for capturing continuous heart rate data. The new watches take heart rate readings every five seconds throughout the day, and more frequently measure heart rate variability (HRV). All of the data collected is sent to the Health app on iPhone. Apple says in a head-to-head study against other wearables using an ECG chest strap as reference, the new Apple Watch had the most accurate heart rate sensing. Apple Intelligence Guidance The Health app will turn the data and metrics that it collects into personalized guidance thanks to Apple Intelligence integration. There are several new sections coming to the Health app. Insights - The Insights tab offers an Apple Intelligence-generated summary of timely information like your latest sleep metrics or a new peak in VO2 max. There are options to get custom advice on readiness, fitness, heart health, and more in the For You section. Personal Guidance - Personal guidance is part of the Insights tab. It knows what's important to you, and will make relevant suggestions. Apple says if you're working on your cardio, you might see a suggestion to incorporate intervals into your morning run. Recommendations adapt to each user and their data. Readiness - The new Apple Watch models calculate a readiness score that takes into account recent activity, vitals, and sleep score. It gives a 0–10 score with recommendations on activity level. Readouts include Recover, Pace Yourself, Ready, or Go For It. Info is shown on the watch, in the Fitness app, and in the Health app's Insights tab. Fitness - Insights incorporates your daily activity and it updates throughout the day. Vitals - The Vitals option in the Health app has new overnight views and daytime views. HRV is incorporated as a metric, offering a better look at your ability to recover from stress. It measures overall HRV and recovery HRV. Longevity - There is a new Longevity tab in the Health app. It uses metrics from your iPhone and Apple Watch to assess overall health across heart health, sleep, mental wellbeing, movement health, metabolic health, hearing, and nutrition. The section shows you how well you're doing in each category, and how each metric is classified against the latest clinical guidance. Health Age - Health Age is part of the Longevity tab. It uses metrics like VO2 max, resting heart rate, HRV, sleep, and biomarkers from blood work to determine how your health metrics compare to your actual age. It will help you figure out what habits make the biggest impact on your health, and how you can improve. Lab Results Health Age and Longevity can be more useful with lab results. Users can upload lab results manually or sync medical records. Apple has also partnered with Quest to offer U.S. users an option to buy a full bloodwork panel that covers more than 50 biomarkers. The test is priced at $119, and users will be able to buy it right in the Health app. It'll require a visit to a Quest lab location, and results are combined with data from the Apple Watch and analyzed on iPhone. Apple says users will get videos from clinical experts related to their results. According to Quest, the panel delivers preventive health insights and includes biomarkers for assessing cardiometabolic health and organ function. It also includes biometric readings that measure blood pressure, height, weight, and waist and hip circumferences. Since the test isn't available in the Health app yet, a full list of what's included isn't known. Apple competitor Oura offers a similar testing option through Quest. The $99 test checks more than 50 biomarkers, and Oura runs discounts. Quest has approximately 2,000 locations across the U.S. Results appear in the Health app shortly after testing. Movement Evaluations Apple is adding new at-home health assessments you can complete, such as a VO2 max test. The test uses the iPhone camera to track your movements as you follow moves and instructions from a trainer. The tests offer real-time audio and visual feedback. There are in-depth physical assessments for measuring flexibility, strength, balance, and movement mechanics in addition to VO2 max. Apple says the tests are useful to see how well your body is moving or to track your progress recovering from an injury. Tests run on device with no video recorded or stored, and users get an exercise plan after completing a test. Cycle Tracking Apple is adding perimenopause and menopause support to Cycle Tracking in the Health app. Device Requirements Apple Watch users with an Apple Intelligence-capable iPhone will get the updated Health app when it launches, but readiness, more frequent heart rate readings, and more frequent HRV readings require a Series 12 or Ultra 4. Launch Date Apple says the new Health app is coming in late 2026, but the company did not give a specific launch date. It will be available in U.S. English at launch, with more languages to follow.Related Roundups: iOS 27, iPadOS 27Tag: Apple HealthRelated Forum: iOS 27This article, "" first appeared on MacRumors.comDiscuss this article in our forums

Read more »

Apple Watch Series 12 Received a Price Increase You Might Have Missed
Ever since the Apple Watch Series 4 in 2018, the larger-sized aluminum Apple Watch has started at $429 in the U.S., but that has changed with the Apple Watch Series 12. While the Apple Watch Series 12 with a 42mm case maintains a starting price of $399, the 46mm model has received a $20 price increase and now starts at $449. In other words, stepping up to a 46mm case now costs an extra $50 instead of $30. Apple products are getting more expensive lately. Amid a RAM chip shortage, the company raised prices on several existing iPhone models this week, after raising prices on Macs, iPads, HomePods, the Apple TV, and more in June. Plus, the starting prices of the iPhone 18 Pro models are $100 higher in the U.S. compared to the iPhone 17 Pro models. Apple Watch Series 12 and Apple Watch Ultra 4 models have increased RAM, according to Xcode.Related Roundup: Apple Watch 11Buyer's Guide: Apple Watch (Don't Buy)Related Forum: Apple WatchThis article, "" first appeared on MacRumors.comDiscuss this article in our forums

Read more »

Ceramic Apple Watch Series 12 Is Bigger and Heavier Than Other Models
Apple Watch Series 12 models with a ceramic case are physically larger than the same model in aluminum or titanium, according to Apple's own tech specs. At 46mm, Apple's tech specs page lists the aluminum and titanium case at 46mm by 40mm by 9.7mm, while the ceramic case sold under the same 46mm name measures 47mm by 41mm by 9.85mm, a millimeter taller, a millimeter wider, and 0.15mm thicker. The 42mm size follows the same pattern: 42mm by 37mm by 9.7mm for aluminum and titanium, versus 43mm by 37mm by 9.85mm for ceramic, a millimeter taller and 0.15mm thicker, with the width unchanged. The display is unaffected. Apple lists the same 1,196 sq mm display area at 46mm and 970 sq mm at 42mm across all three materials, meaning the extra size is entirely case, not screen. The ceramic models are also heavier. At 46mm, the Pearl White ceramic case weighs 51.3 grams and Night Blue weighs 52.9 grams, against 39.5 grams for the equivalent aluminum model and 44.9 grams for titanium, up to 34% heavier than aluminum and 18% heavier than titanium. The 42mm ceramic models weigh 41.7 grams in Pearl White and 42.8 grams in Night Blue, against 32.2 grams for aluminum and 36.5 grams for titanium, up to 33% heavier than aluminum and 17% heavier than titanium. This appears to be the first time Apple has sold different physical case dimensions under the same nominal watch size. The increased size is presumably a design compromise owing to the entirely different material, although the earlier ceramic Apple Watch Edition models used identical case dimensions across materials at a given size, with only the weight changing between them. Ceramic returns to the Apple Watch lineup with the Series 12 after a six-year absence, having last been offered on Series 5 in 2019 before Apple dropped it for Series 6 in 2020. Apple Watch Series 12 in ceramic starts at $899, compared with $399 for aluminum and $699 for titanium, in Pearl White or Night Blue finishes. It launches on September 18.Related Roundup: Apple Watch 11Buyer's Guide: Apple Watch (Don't Buy)Related Forum: Apple WatchThis article, "" first appeared on MacRumors.comDiscuss this article in our forums

Read more »

Skipping the iPhone 18 Pro? Redesigned 'iPhone 20' is Coming Next Year
Apple unveiled the iPhone 18 Pro models just one day ago, but there are already rumors about a redesigned "iPhone 20" launching next September. Bloomberg's Mark Gurman recently reported that Apple plans to release a special 20th-anniversary iPhone next year with the biggest design changes since the iPhone X. Of course, there is always a new iPhone around the corner, but it sounds like the so-called "iPhone 20" will have significant changes that some customers may wish to wait for. Unveiled by Steve Jobs in 2007, the iPhone turns 20 next year. To mark the occasion, the report said Apple plans to release a 20th-anniversary iPhone with "curved glass around all corners and edges" and thinner bezels around the screen. "It will be the biggest overhaul to what is now the iPhone Pro line since the iPhone X," the report said, but no further details were provided. Released in 2017, the iPhone X was the first iPhone with Face ID. The removal of the Touch ID button allowed for the iPhone X's screen to extend more towards the edges of the device compared to previous models. It seems like the 20th-anniversary iPhone would go a step further than this by truly having the screen wrap around the corners and edges of the device, for a seemingly all-glass appearance. Rumors about the 20th-anniversary iPhone have gone back and forth, but based on Gurman's latest reporting, the device seems to be in the works still. However, it remains to be seen if Apple can fully achieve the ambitious design changes that are apparently in development, or if plans for the device will ultimately be scaled back. As for the iPhone 18 Pro, key new features include an A20 Pro chip with up to a 20% faster CPU and up to a 40% faster GPU compared to the A19 Pro chip, a smaller Dynamic Island, variable aperture for the main 48-megapixel Fusion camera, longer battery life, and a larger vapor chamber cooling system for improved heat dissipation. If those upgrades do not sound interesting to you, waiting for the redesigned "iPhone 20" might prove to be worthwhile, but only if rumors come to fruition.Related Roundup: iPhone 18 ProTag: 20th-Anniversary iPhoneThis article, "" first appeared on MacRumors.comDiscuss this article in our forums

Read more »

Apple Watch Series 12 Has Smaller Screens and Bigger Cases
The Apple Watch Series 12 pairs a smaller display with a wider case than Series 10 and Series 11, even though the pixel resolution hasn't changed, according to Apple's own tech specs. For the 46mm Series 12, Apple's tech specs page lists the display area at 1,196 sq mm, down 2% from 1,220 sq mm on Series 10 and Series 11. The 42mm size shows a similar 1.9% drop, from 989 sq mm to 970 sq mm. Pixel counts are identical across all three generations: 416 by 496 at 46mm, and 374 by 446 at 42mm. The case grows as the screen shrinks. Apple's Series 12 tech specs list the 46mm case at 46mm by 40mm by 9.7mm, a millimeter wider than the 46mm by 39mm by 9.7mm case on Series 10 and Series 11, a roughly 2.6% increase in case footprint. The 42mm case grew from 42mm by 36mm to 42mm by 37mm over the same span, about 2.8%, with depth unchanged at 9.7mm for both sizes. A smaller display combined with a bigger casing means bigger borders around the display, and it looks like Apple has also tweaked the design of the Series 12 to recede the casing and expand the front glass, which makes the borders look even larger. There's recent precedent for a change like this translating into a visibly thicker bezel. Series 10 went through a similar shift when it replaced Series 9 in 2024, growing the case around the display. The Series 10's visible aluminum edge had actually shrunk by around 33% versus Series 9, while the total bezel, including the black glass border, had grown by about 17%, even though the case and display figures looked like an improvement on paper. It looks like the Series 12 repeats that pattern, although to a less extreme extent. Unlike the Series 9 to Series 10 change, which was a full case redesign, Series 10, Series 11, and Series 12 all share the same approximate case design. The Apple Watch Series 12 starts at $399 and launches on September 18.Related Roundup: Apple Watch 11Buyer's Guide: Apple Watch (Don't Buy)This article, "" first appeared on MacRumors.comDiscuss this article in our forums

Read more »

Apple Watch Series 12 Has Smaller Screens and Bigger Cases
The Apple Watch Series 12 pairs a smaller display with a wider case than Series 10 and Series 11, even though the pixel resolution hasn't changed, according to Apple's own tech specs. For the 46mm Series 12, Apple's tech specs page lists the display area at 1,196 sq mm, down 2% from 1,220 sq mm on Series 10 and Series 11. The 42mm size shows a similar 1.9% drop, from 989 sq mm to 970 sq mm. Pixel counts are identical across all three generations: 416 by 496 at 46mm, and 374 by 446 at 42mm. The case grows as the screen shrinks. Apple's Series 12 tech specs list the 46mm case at 46mm by 40mm by 9.7mm, a millimeter wider than the 46mm by 39mm by 9.7mm case on Series 10 and Series 11, a roughly 2.6% increase in case footprint. The 42mm case grew from 42mm by 36mm to 42mm by 37mm over the same span, about 2.8%, with depth unchanged at 9.7mm for both sizes. A smaller display combined with a bigger casing means bigger borders around the display, and it looks like Apple has also tweaked the design of the Series 12 to recede the casing and expand the front glass, which makes the borders look even larger. There's recent precedent for a change like this translating into a visibly thicker bezel. Series 10 went through a similar shift when it replaced Series 9 in 2024, growing the case around the display. The Series 10's visible aluminum edge had actually shrunk by around 33% versus Series 9, while the total bezel, including the black glass border, had grown by about 17%, even though the case and display figures looked like an improvement on paper. It looks like the Series 12 repeats that pattern, although to a less extreme extent. Unlike the Series 9 to Series 10 change, which was a full case redesign, Series 10, Series 11, and Series 12 all share the same approximate case design. The Apple Watch Series 12 starts at $399 and launches on September 18.Related Roundup: Apple Watch 11Buyer's Guide: Apple Watch (Don't Buy)This article, "" first appeared on MacRumors.comDiscuss this article in our forums

Read more »

Apple Watch Series 12 Has Smaller Screens and Bigger Cases
The Apple Watch Series 12 pairs a smaller display with a wider case than Series 10 and Series 11, even though the pixel resolution hasn't changed, according to Apple's own tech specs. For the 46mm Series 12, Apple's tech specs page lists the display area at 1,196 sq mm, down 2% from 1,220 sq mm on Series 10 and Series 11. The 42mm size shows a similar 1.9% drop, from 989 sq mm to 970 sq mm. Pixel counts are identical across all three generations: 416 by 496 at 46mm, and 374 by 446 at 42mm. The case grows as the screen shrinks. Apple's Series 12 tech specs list the 46mm case at 46mm by 40mm by 9.7mm, a millimeter wider than the 46mm by 39mm by 9.7mm case on Series 10 and Series 11, a roughly 2.6% increase in case footprint. The 42mm case grew from 42mm by 36mm to 42mm by 37mm over the same span, about 2.8%, with depth unchanged at 9.7mm for both sizes. A smaller display combined with a bigger casing means bigger borders around the display, and it looks like Apple has also tweaked the design of the Series 12 to recede the casing and expand the front glass, which makes the borders look even larger. There's recent precedent for a change like this translating into a visibly thicker bezel. Series 10 went through a similar shift when it replaced Series 9 in 2024, growing the case around the display. The Series 10's visible aluminum edge had actually shrunk by around 33% versus Series 9, while the total bezel, including the black glass border, had grown by about 17%, even though the case and display figures looked like an improvement on paper. It looks like the Series 12 repeats that pattern, although to a less extreme extent. Unlike the Series 9 to Series 10 change, which was a full case redesign, Series 10, Series 11, and Series 12 all share the same approximate case design. The Apple Watch Series 12 starts at $399 and launches on September 18.Related Roundup: Apple Watch 11Buyer's Guide: Apple Watch (Don't Buy)This article, "" first appeared on MacRumors.comDiscuss this article in our forums

Read more »

Apple Watch Series 12 Has Smaller Screens and Bigger Cases
The Apple Watch Series 12 pairs a smaller display with a wider case than Series 10 and Series 11, even though the pixel resolution hasn't changed, according to Apple's own tech specs. For the 46mm Series 12, Apple's tech specs page lists the display area at 1,196 sq mm, down 2% from 1,220 sq mm on Series 10 and Series 11. The 42mm size shows a similar 1.9% drop, from 989 sq mm to 970 sq mm. Pixel counts are identical across all three generations: 416 by 496 at 46mm, and 374 by 446 at 42mm. The case grows as the screen shrinks. Apple's Series 12 tech specs list the 46mm case at 46mm by 40mm by 9.7mm, a millimeter wider than the 46mm by 39mm by 9.7mm case on Series 10 and Series 11, a roughly 2.6% increase in case footprint. The 42mm case grew from 42mm by 36mm to 42mm by 37mm over the same span, about 2.8%, with depth unchanged at 9.7mm for both sizes. A smaller display combined with a bigger casing means bigger borders around the display, and it looks like Apple has also tweaked the design of the Series 12 to recede the casing and expand the front glass, which makes the borders look even larger. There's recent precedent for a change like this translating into a visibly thicker bezel. Series 10 went through a similar shift when it replaced Series 9 in 2024, growing the case around the display. The Series 10's visible aluminum edge had actually shrunk by around 33% versus Series 9, while the total bezel, including the black glass border, had grown by about 17%, even though the case and display figures looked like an improvement on paper. It looks like the Series 12 repeats that pattern, although to a less extreme extent. Unlike the Series 9 to Series 10 change, which was a full case redesign, Series 10, Series 11, and Series 12 all share the same approximate case design. The Apple Watch Series 12 starts at $399 and launches on September 18.Related Roundup: Apple Watch 11Buyer's Guide: Apple Watch (Don't Buy)This article, "" first appeared on MacRumors.comDiscuss this article in our forums

Read more »

Apple Watch Series 12 Has Smaller Screens and Bigger Cases
The Apple Watch Series 12 pairs a smaller display with a wider case than Series 10 and Series 11, even though the pixel resolution hasn't changed, according to Apple's own tech specs. For the 46mm Series 12, Apple's tech specs page lists the display area at 1,196 sq mm, down 2% from 1,220 sq mm on Series 10 and Series 11. The 42mm size shows a similar 1.9% drop, from 989 sq mm to 970 sq mm. Pixel counts are identical across all three generations: 416 by 496 at 46mm, and 374 by 446 at 42mm. The case grows as the screen shrinks. Apple's Series 12 tech specs list the 46mm case at 46mm by 40mm by 9.7mm, a millimeter wider than the 46mm by 39mm by 9.7mm case on Series 10 and Series 11, a roughly 2.6% increase in case footprint. The 42mm case grew from 42mm by 36mm to 42mm by 37mm over the same span, about 2.8%, with depth unchanged at 9.7mm for both sizes. A smaller display combined with a bigger casing means bigger borders around the display, and it looks like Apple has also tweaked the design of the Series 12 to recede the casing and expand the front glass, which makes the borders look even larger. There's recent precedent for a change like this translating into a visibly thicker bezel. Series 10 went through a similar shift when it replaced Series 9 in 2024, growing the case around the display. The Series 10's visible aluminum edge had actually shrunk by around 33% versus Series 9, while the total bezel, including the black glass border, had grown by about 17%, even though the case and display figures looked like an improvement on paper. It looks like the Series 12 repeats that pattern, although to a less extreme extent. Unlike the Series 9 to Series 10 change, which was a full case redesign, Series 10, Series 11, and Series 12 all share the same approximate case design. The Apple Watch Series 12 starts at $399 and launches on September 18.Related Roundup: Apple Watch 11Buyer's Guide: Apple Watch (Don't Buy)This article, "" first appeared on MacRumors.comDiscuss this article in our forums

Read more »

Apple Watch Series 12 Has Smaller Screens and Bigger Cases
The Apple Watch Series 12 pairs a smaller display with a wider case than Series 10 and Series 11, even though the pixel resolution hasn't changed, according to Apple's own tech specs. For the 46mm Series 12, Apple's tech specs page lists the display area at 1,196 sq mm, down 2% from 1,220 sq mm on Series 10 and Series 11. The 42mm size shows a similar 1.9% drop, from 989 sq mm to 970 sq mm. Pixel counts are identical across all three generations: 416 by 496 at 46mm, and 374 by 446 at 42mm. The case grows as the screen shrinks. Apple's Series 12 tech specs list the 46mm case at 46mm by 40mm by 9.7mm, a millimeter wider than the 46mm by 39mm by 9.7mm case on Series 10 and Series 11, a roughly 2.6% increase in case footprint. The 42mm case grew from 42mm by 36mm to 42mm by 37mm over the same span, about 2.8%, with depth unchanged at 9.7mm for both sizes. A smaller display combined with a bigger casing means bigger borders around the display, and it looks like Apple has also tweaked the design of the Series 12 to recede the casing and expand the front glass, which makes the borders look even larger. There's recent precedent for a change like this translating into a visibly thicker bezel. Series 10 went through a similar shift when it replaced Series 9 in 2024, growing the case around the display. The Series 10's visible aluminum edge had actually shrunk by around 33% versus Series 9, while the total bezel, including the black glass border, had grown by about 17%, even though the case and display figures looked like an improvement on paper. It looks like the Series 12 repeats that pattern, although to a less extreme extent. Unlike the Series 9 to Series 10 change, which was a full case redesign, Series 10, Series 11, and Series 12 all share the same approximate case design. The Apple Watch Series 12 starts at $399 and launches on September 18.Related Roundup: Apple Watch 11Buyer's Guide: Apple Watch (Don't Buy)This article, "" first appeared on MacRumors.comDiscuss this article in our forums

Read more »

How to check your Mac for malware (and what to do if you find it)
9 things you can do if you think your Mac has malware. The post first appeared on The Mac Security Blog.

Read more »

How to check your Mac for malware (and what to do if you find it)
9 things you can do if you think your Mac has malware. The post first appeared on The Mac Security Blog.

Read more »

Vulnerability Summary for the Week of August 17, 2026
High Vulnerabilities PrimaryVendor -- Product Description Published CVSS Score Source Info 101gen--Automation Web Platform Notifications and OTP for WooCommerce, Advanced Country Code The Automation Web Platform - Notifications and OTP for WooCommerce, Advanced Country Code plugin for WordPress is vulnerable to Authentication Bypass in versions up to, and including, 4.8.6. This is due to the handle_email_otp_return() function returning the secret magic login token in the response to a publicly accessible OTP request, rather than only delivering it to the user's email address. This makes it possible for unauthenticated attackers to log in as any user on the site, including administrators, if they know that user's email address. 2026-08-21 9.8 CVE-2026-77264 10Web--Form Maker by 10Web Unauthenticated Cross Site Scripting (XSS) in Form Maker by 10Web = 0.8.41 and < 0.8.64 contain a vulnerability in the exec_shell_interact (alias exec_interact) tool, whose approval_requirement returns ApprovalRequirement::Auto. This overrides the default Required approval for code-executing tools, so LLM-controlled stdin is written into an already-approved long-running interactive shell (e.g., a python3 -i REPL, mysql, ssh, or sudo -i session) without any approval prompt. An attacker who can inject instructions via untrusted content the agent ingests (a fetched page, MCP result, or repo file) can cause commands to run at the privilege level of that approved process. Fixed in 0.8.64. 2026-08-18 7 CVE-2026-75857 Hmbown--CodeWhale CodeWhale (packages codewhale / codewhale-tui) versions >= 0.8.41 and < 0.8.64 contain a remote code execution vulnerability in the rlm_eval tool. The tool's approval_requirement() returns ApprovalRequirement::Auto, which the engine treats as 'never prompt,' causing arbitrary model-supplied Python code to run in a python3 interpreter without consulting the user's configured --approval-policy and without any approval prompt or audit step. An attacker can induce the agent to execute arbitrary code via prompt injection in untrusted content the agent reads (a web page, fetched URL, repository file, or MCP tool result); the companion rlm_open tool can stage such content. Code runs on the user's machine at the user's privilege level. Fixed in 0.8.64. 2026-08-18 7.8 CVE-2026-75858 Hmbown--CodeWhale CodeWhale versions before 0.8.64 fail to validate file paths in the project config instructions field, allowing attackers to read arbitrary files on the victim's system. A malicious .codewhale/config.toml file in a cloned repository can specify paths outside the workspace that are read and injected into the AI system prompt for exfiltration. 2026-08-18 7.5 CVE-2026-75859 Hmbown--CodeWhale CodeWhale versions before 0.8.64 fail to properly validate the allow_shell configuration parameter from project config files, allowing attackers to enable arbitrary shell command execution by committing a malicious .codewhale/config.toml file to a repository. When a user clones and opens the repository in CodeWhale, the AI model gains access to exec_shell and task_shell tools, enabling execution of arbitrary shell commands on the victim's machine without explicit user consent. 2026-08-18 7.8 CVE-2026-75911 Hmbown--CodeWhale CodeWhale versions before 0.8.64 contain an argument injection vulnerability in the git_blame tool that allows attackers to read arbitrary files by injecting git options into the unvalidated rev parameter. Attackers can supply rev values like --contents=/path/to/file to exfiltrate sensitive files such as SSH keys and credentials through the tool output returned to the model. 2026-08-18 7.4 CVE-2026-75912 Hmbown--CodeWhale CodeWhale versions before 0.8.64 contain a path traversal vulnerability in the image_analyze tool that fails to canonicalize symlinks before reading files. Attackers can create workspace symlinks pointing to external files with image extensions to leak file bytes to the vision endpoint without user approval. 2026-08-18 7.5 CVE-2026-75914 Hmbown--CodeWhale CodeWhale versions before 0.8.64 contain an environment variable exposure vulnerability in the js_execution tool that fails to scrub parent process environment variables before spawning Node.js. Attackers can craft malicious JavaScript code executed by the tool to read process.env and leak API keys, cloud credentials, and authentication tokens back to the model context. 2026-08-18 7.5 CVE-2026-75915 hoppscotch--hoppscotch Hoppscotch is an open source API development ecosystem. Prior to 2026.6.0, the team, teamMembers.user, RESTHistory, GQLHistory, currentRESTSession, currentGQLSession, environments, globalEnvironments, and settings GraphQL paths expose another workspace member's private User data, while toggleHistoryStarStatus and removeRequestFromHistory in the UserHistory service accept another user's history identifier without enforcing userUid ownership, allowing an authenticated workspace member to read private request history, session data, request contents, authorization headers, environment values, and settings and to modify or delete the victim's private history entries. This issue is fixed in version 2026.6.0. 2026-08-18 7.6 CVE-2026-69189 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 NIM could allow a remote attacker to bypass security restrictions due to the exposure of intermediate certificate authority private keys in a publicly available update file. 2026-08-19 9.1 CVE-2026-15065 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 NIM could allow a remote authenticated attacker to execute arbitrary commands due to improper neutralization of special elements used in an OS command. 2026-08-19 9.9 CVE-2026-15068 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to gain root privileges due to improper authentication. 2026-08-19 9.8 CVE-2026-16656 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote authenticated attacker to execute arbitrary commands due to improper neutralization of special elements used in an OS command. 2026-08-19 9.9 CVE-2026-16816 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to impersonate the TNC policy server and modify traffic due to improper certificate validation. 2026-08-19 9.3 CVE-2026-16822 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to cause a denial of service due to an integer underflow. 2026-08-19 9.8 CVE-2026-16834 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to obtain sensitive information due to an integer underflow in the IPv4 IP-options parser. 2026-08-19 9.4 CVE-2026-16839 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to an out-of-bounds write. 2026-08-19 9.8 CVE-2026-16840 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to a heap buffer overflow. 2026-08-19 9.8 CVE-2026-16845 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to a stack buffer overflow. 2026-08-19 9.8 CVE-2026-16862 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to a stack buffer overflow. 2026-08-19 9.8 CVE-2026-16864 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to a stack-based buffer overflow. 2026-08-19 9.8 CVE-2026-16872 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary commands due to improper neutralization of special elements used in an OS command. 2026-08-19 9.8 CVE-2026-16882 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to a stack buffer overflow. 2026-08-19 9.8 CVE-2026-16885 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to a stack buffer overflow. 2026-08-19 9.8 CVE-2026-16894 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code or cause a denial of service due to an out-of-bounds write. 2026-08-19 9.6 CVE-2026-16903 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to a stack buffer overflow. 2026-08-19 9.8 CVE-2026-16913 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to an integer overflow. 2026-08-19 9.8 CVE-2026-16917 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to improper validation of network-supplied pointers. 2026-08-19 9.8 CVE-2026-16919 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to overwrite arbitrary files due to improper neutralization of special elements in input. 2026-08-20 9.1 CVE-2026-16926 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to a buffer overflow. 2026-08-20 9.8 CVE-2026-17040 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to a use-after-free vulnerability. 2026-08-20 9.8 CVE-2026-17118 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to a stack-based buffer overflow. 2026-08-20 9.8 CVE-2026-17122 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to a format string vulnerability. 2026-08-20 9.8 CVE-2026-17136 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to a buffer overflow. 2026-08-20 9.8 CVE-2026-17141 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary commands due to improper authentication. 2026-08-20 9.8 CVE-2026-17142 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to improper privilege management. 2026-08-20 9.8 CVE-2026-17145 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to a buffer overflow. 2026-08-20 9.8 CVE-2026-17152 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to a stack buffer overflow. 2026-08-20 9.8 CVE-2026-17157 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to an integer overflow during size computation. 2026-08-20 9.8 CVE-2026-17160 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to execute arbitrary code due to a buffer overflow. 2026-08-20 9.3 CVE-2026-17422 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote authenticated attacker to execute arbitrary commands due to improper neutralization of special elements used in an OS command. 2026-08-20 9.9 CVE-2026-18835 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 's nimesis registration service could allow a remote attacker to overwrite files due to path traversal. 2026-08-19 8.2 CVE-2026-15061 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 NIM could allow a remote attacker to gain unauthorized access to AIX systems due to improper validation of TLS certificates. 2026-08-19 8.1 CVE-2026-15078 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to access NFS-exported filesystems due to improper authentication. 2026-08-19 8.2 CVE-2026-16686 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to a heap buffer overflow. 2026-08-19 8.8 CVE-2026-16814 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to a stack buffer overflow. 2026-08-19 8.8 CVE-2026-16841 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary commands due to improper neutralization of special elements used in an OS command. 2026-08-19 8.8 CVE-2026-16842 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary commands due to improper neutralization of special elements used in an OS command. 2026-08-19 8.8 CVE-2026-16844 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to a heap buffer overflow. 2026-08-19 8.8 CVE-2026-16847 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary commands due to improper neutralization of shell metacharacters in DHCP options. 2026-08-19 8.8 CVE-2026-16848 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to command injection via crafted Router Advertisements. 2026-08-19 8.8 CVE-2026-16850 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to manipulate network traffic and DNS configuration due to improper authentication. 2026-08-19 8.2 CVE-2026-16857 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to command injection. 2026-08-19 8.8 CVE-2026-16865 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote authenticated attacker to execute arbitrary code due to a stack-based buffer overflow. 2026-08-19 8.8 CVE-2026-16877 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to an out-of-bounds write. 2026-08-19 8.8 CVE-2026-16901 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to an off-by-one error in bounds checking. 2026-08-19 8.8 CVE-2026-16909 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote authenticated attacker to execute arbitrary code due to a stack buffer overflow. 2026-08-19 8.8 CVE-2026-16911 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to execute arbitrary commands due to improper validation of the ODMDIR environment variable. 2026-08-20 8.8 CVE-2026-16932 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to gain elevated privileges due to a heap-based buffer overflow. 2026-08-20 8.8 CVE-2026-16934 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to execute arbitrary code due to a buffer overflow. 2026-08-20 8.8 CVE-2026-16936 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to execute arbitrary code due to a heap-based buffer overflow. 2026-08-20 8.2 CVE-2026-16943 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to execute arbitrary code due to an integer underflow. 2026-08-20 8.8 CVE-2026-16996 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to improper authentication. 2026-08-20 8.1 CVE-2026-17000 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to a heap buffer overflow. 2026-08-20 8.3 CVE-2026-17006 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to obtain sensitive information and cause a denial of service due to a kernel heap over-read. 2026-08-20 8.1 CVE-2026-17060 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to a stack-based buffer overflow. 2026-08-20 8.1 CVE-2026-17138 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote authenticated attacker to execute arbitrary code due to a stack-based buffer overflow. 2026-08-20 8.5 CVE-2026-17168 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to a heap-based buffer overflow. 2026-08-20 8.8 CVE-2026-17436 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to cause a denial of service and potentially disclose sensitive information due to an integer underflow. 2026-08-20 8.2 CVE-2026-18670 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote authenticated attacker to execute arbitrary commands due to improper neutralization of special elements used in an OS command. 2026-08-20 8.4 CVE-2026-18824 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to a heap-based buffer overflow. 2026-08-20 8.8 CVE-2026-18832 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to execute arbitrary code due to improper validation of an attacker-controlled pointer. 2026-08-20 8.2 CVE-2026-18840 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to gain elevated privileges due to an out-of-bounds write. 2026-08-20 8.4 CVE-2026-18842 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to a buffer overflow. 2026-08-20 8.1 CVE-2026-19437 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 has a pointer validation flaw exists in the AIX Virtual SCSI (vSCSI) initiator driver. Successful exploitation may result in denial of service, privilege escalation, or full compromise of the client LPAR kernel. 2026-08-20 8.2 CVE-2026-19442 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 has a vulnerability in cmdnim that may allow an unprivileged local user to executes the payload as root. 2026-08-20 8.8 CVE-2026-19449 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 NIM server process is crashing during client registration due to buffer overflow. 2026-08-19 7.5 CVE-2026-14970 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to cause a denial of service due to uncontrolled resource consumption. 2026-08-19 7.5 CVE-2026-16690 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to gain elevated privileges due to improper privilege management. 2026-08-19 7.8 CVE-2026-16703 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to cause a denial of service due to an out-of-bounds write. 2026-08-19 7.5 CVE-2026-16706 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to cause a denial of service due to a NULL pointer dereference. 2026-08-19 7.5 CVE-2026-16817 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to cause a denial of service due to uncontrolled resource consumption. 2026-08-19 7.5 CVE-2026-16818 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to cause a denial of service and compromise data integrity due to a time-of-check time-of-use race condition. 2026-08-19 7.7 CVE-2026-16819 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to cause a denial of service due to unbounded recursion. 2026-08-19 7.5 CVE-2026-16824 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to cause a denial of service due to uncontrolled resource consumption. 2026-08-19 7.5 CVE-2026-16831 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to cause a denial of service due to uncontrolled resource consumption. 2026-08-19 7.5 CVE-2026-16836 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to cause a denial of service due to improper handling of a missing SSL client certificate. 2026-08-19 7.5 CVE-2026-16837 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to overwrite critical files and obtain sensitive information due to a time-of-check to time-of-use (TOCTOU) race condition. 2026-08-19 7 CVE-2026-16838 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to cause a denial of service due to a use-after-free. 2026-08-19 7.4 CVE-2026-16851 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to cause a denial of service due to an integer overflow. 2026-08-19 7.5 CVE-2026-16852 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to execute arbitrary code due to improperly scrubbed environment variables. 2026-08-19 7.8 CVE-2026-16869 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to achieve local privilege escalation due to an out-of-bounds write. 2026-08-19 7.8 CVE-2026-16873 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to obtain root privileges due to improper enforcement of RBAC authentication roles. 2026-08-19 7.8 CVE-2026-16874 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to execute arbitrary commands due to shell metacharacter injection. 2026-08-19 7.8 CVE-2026-16875 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to execute arbitrary code due to a time-of-check to time-of-use (TOCTOU) race condition. 2026-08-20 7 CVE-2026-16922 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to gain elevated privileges due to improper privilege management. 2026-08-20 7 CVE-2026-16923 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to cause a denial of service due to an improper calculation of a memory offset during IPsec decapsulation. 2026-08-20 7.5 CVE-2026-16924 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to achieve privilege escalation due to improper authorization. 2026-08-20 7.1 CVE-2026-16925 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to gain root privileges due to a time-of-check to time-of-use (TOCTOU) race condition. 2026-08-20 7.3 CVE-2026-16927 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to cause a denial of service due to a heap-based buffer overflow. 2026-08-20 7.5 CVE-2026-16928 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to gain elevated privileges due to a time-of-check to time-of-use (TOCTOU) race condition. 2026-08-20 7.8 CVE-2026-16935 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to gain elevated privileges due to improper privilege management. 2026-08-20 7.8 CVE-2026-16937 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to execute arbitrary code due to a stack-based buffer overflow. 2026-08-20 7.8 CVE-2026-16945 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to gain elevated privileges due to a heap buffer overflow. 2026-08-20 7.8 CVE-2026-16946 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to gain elevated privileges due to improper resolution of symbolic links. 2026-08-20 7.1 CVE-2026-16989 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to gain elevated privileges due to improper handling of symbolic links. 2026-08-20 7.8 CVE-2026-16991 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to execute arbitrary commands due to improper privilege management. 2026-08-20 7.8 CVE-2026-16997 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to compromise the confidentiality and integrity of the system due to an out-of-bounds write. 2026-08-20 7.7 CVE-2026-17003 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to improper certificate validation. 2026-08-20 7.7 CVE-2026-17024 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to cause a denial of service due to uncontrolled recursion. 2026-08-20 7.5 CVE-2026-17121 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to execute arbitrary code due to an out-of-bounds read. 2026-08-20 7.8 CVE-2026-17124 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to cause a denial of service due to an integer overflow. 2026-08-20 7.5 CVE-2026-17159 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to cause a denial of service due to improper validation of an array size field. 2026-08-20 7.5 CVE-2026-17163 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to cause a denial of service due to a NULL pointer dereference. 2026-08-20 7.5 CVE-2026-17165 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to cause a denial of service due to improper validation of an allocation size. 2026-08-20 7.5 CVE-2026-17170 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to overwrite arbitrary files due to improper resolution of symbolic links. 2026-08-20 7.8 CVE-2026-17171 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to obtain sensitive information and cause a denial of service due to an out-of-bounds read. 2026-08-20 7.7 CVE-2026-17423 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to cause a denial of service due to a stack buffer overflow. 2026-08-20 7.5 CVE-2026-17425 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote authenticated attacker to obtain sensitive information or cause a denial of service due to an out-of-bounds read. 2026-08-20 7.9 CVE-2026-18716 IBM--AIX IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 allows a remote unauthenticated attacker can send a crafted UDP packet to a reachable RPC service, resulting in complete system unavailability and requiring an LPAR restart. 2026-08-20 7.5 CVE-2026-19446 IBM--DS8A00 (R10.0 - R10.1) IBM System Storage DS8A00 10.1.3.0 through 10.11.35.0 and IBM DS8900F 89.40.83.0 through 89.44.25.0 could allow an attacker to bypass security authentication due to improperly encoding of DSCLI command output to obtain sensitive information or cause a denial of service. 2026-08-19 7.4 CVE-2025-36254 IBM--DS8A00( R10.0 - R10.1 ) IBM System Storage DS8A00 10.1.3.0 through 10.11.35.0 and IBM DS8900F 89.40.83.0 through 89.44.25.0 could allow an authenticated user to create a user with privileged user roles due to improper privileged defined with unsafe actions. 2026-08-19 7.5 CVE-2025-36255 IBM--Langflow OSS IBM Langflow OSS 1.0.0 through 1.10.0 could allow a remote attacker to overwrite administrator email information and abuse the server as an outbound relay due to missing authentication for the registration endpoint. 2026-08-19 7.5 CVE-2026-19875 IBM--Portieris IBM Portieris 0.5.0 through 0.14.2 could allow a remote authenticated attacker to bypass image policy enforcement due to improper authorization of pod owner references. 2026-08-19 8.1 CVE-2026-18544 IBM--Power Systems Firmware IBM Power Systems Firmware FW1120.00, FW1110.00 through FW1110.30, FW1060.00 through FW1060.80, and FW950.00 through FW950.H2 is affected by a vulnerability in the ASMI web interface. An unauthenticated attacker with network access can send the FSP a malformed request, allowing arbitrary code execution, giving the attacker full control over the managed system, resulting in a confidentiality, integrity, and availability impact. 2026-08-19 9.6 CVE-2026-16687 IBM--Power Systems Firmware IBM Power Systems Firmware FW1120.00, FW1110.00 through FW1110.30, FW1060.00 through FW1060.80, and FW950.00 through FW950.H2 is affected by a vulnerability in the FSP management network protocol. An unauthenticated attacker on the management network can bypass authentication and perform any administrative operation on the managed system, including control of partition power state, configuration, and console access across all hosted partitions, resulting in a confidentiality, integrity, and availability impact to the managed system. 2026-08-19 9.6 CVE-2026-16835 IBM--Power Systems Firmware IBM Power Systems Firmware FW1120.00, FW1110.00 through FW1110.30, FW1060.00 through FW1060.80, and FW950.00 through FW950.H2 is affected by a vulnerability in the FSP management network protocol. An attacker with authenticated HMC administrator access can execute arbitrary code on the service processor, giving full control over the managed system, resulting in a confidentiality, integrity, and availability impact. 2026-08-19 8.4 CVE-2026-16832 IBM--Power Systems Firmware IBM Power Systems Firmware FW1120.00, FW1110.00 through FW1110.30, and FW1060.00 through FW1060.80 is affected by a vulnerability in the interface between the BMC/FSP and the host system. An attacker with service account or root access to the BMC/FSP can execute arbitrary code on the host system, giving full control over the host system and all hosted partitions, resulting in a confidentiality, integrity, and availability impact. 2026-08-19 8.2 CVE-2026-16930 IBM--Power Systems Firmware IBM Power Systems Firmware FW1120.00, FW1110.00 through FW1110.30, FW1060.00 through FW1060.80, FW950.00 through FW950.H2, OP940.00 through OP940.a1 (Power9), and OP940.00 through OP940.81 (Power HMC) is affected by a vulnerability in the interface between the BMC/FSP and the host system. An attacker with service account or root access to the BMC/FSP can read and write arbitrary regions of host system memory, giving full control over the host system and all hosted partitions, resulting in a confidentiality, integrity, and availability impact. 2026-08-19 8.2 CVE-2026-16933 IBM--Power Systems Firmware IBM Power Systems Firmware FW1120.00, FW1110.00 through FW1110.30, FW1060.00 through FW1060.80, FW950.00 through FW950.H2, OP940.00 through OP940.a1 (Power9), and OP940.00 - OP940.81 (Power HMC) is affected by a vulnerability in host firmware configuration parsing. An attacker with service-level access to the BMC/FSP can supply specially crafted configuration data, compromising the host firmware boot stage and everything subsequently loaded by it, resulting in a confidentiality, integrity, and availability impact to the managed system. 2026-08-19 8.2 CVE-2026-17093 IBM--Power Systems Firmware Power Systems Firmware FW1120.00, FW1110.00 through FW1110.30, FW1060.00 through FW1060.80, FW950.00 through FW950.H2, OP940.00 through OP940.a1, and OP940.00 - OP940.81 is affected by a vulnerability in the service processor mailbox interface. An attacker with authenticated service-level access to the BMC/FSP can exploit this vulnerability, allowing arbitrary code to be executed in the host firmware runtime, giving full control over the managed system, resulting in a confidentiality, integrity, and availability impact to the managed system. 2026-08-19 8.2 CVE-2026-17100 IBM--Power Systems Firmware IBM Power Systems Firmware FW1120.00, FW1110.00 through FW1110.30, FW1060.00 through FW1060.80, FW950.00 through FW950.H2, OP940.00 through OP940.a1 (Power9), and OP940.00 - OP940.81 (Power HMC) is affected by a vulnerability in the interface between the BMC/FSP and the host system. An attacker with service account or root access to the BMC/FSP can write arbitrary data to hardware control registers, allowing full control over the host system and all hosted partitions, resulting in a confidentiality, integrity, and availability impact. 2026-08-19 8.1 CVE-2026-17429 IBM--Power Systems Firmware IBM Power Systems Firmware FW1120.00, and FW1110.00 through FW1110.30 is affected by a vulnerability in the interface between the BMC and the host system. An attacker with service access to the BMC can send a specially crafted command, allowing arbitrary code to be executed on the host system, giving full control over the host system and all hosted partitions, resulting in a confidentiality, integrity, and availability impact. 2026-08-19 8.2 CVE-2026-17494 IBM--Power Systems Firmware IBM Power Systems Firmware FW1120.00, FW1110.00 through FW1110.30, FW1060.00 through FW1060.80, and FW950.00 through FW950.H2 is affected by a vulnerability in the ASMI web interface. An attacker who can lure a logged-in ASMI administrator to visit a crafted web page can, under specific conditions, silently perform administrative actions on the FSP on behalf of that administrator, resulting in a confidentiality, integrity, and availability impact to the managed system. 2026-08-19 8.3 CVE-2026-18848 IBM--Power Systems Firmware Power Systems Firmware FW1120.00, FW1110.00 through FW1110.30, and FW1060.00 through FW1060.80 is affected by a vulnerability in the host firmware boot process image validation path. An attacker with service access to the service processor can supply a maliciously crafted code update image, allowing arbitrary code to be executed on the host system. Successful exploitation could result in a confidentiality, integrity, and availability impact to the affected host system. 2026-08-19 8.2 CVE-2026-19234 IBM--Power Systems Firmware IBM Power Systems Firmware FW1120.00, FW1110.00 through FW1110.30, FW1060.00 through FW1060.80, and FW950.00 through FW950.H2 is affected by a vulnerability in the ASMI web interface. An unauthenticated attacker on the management network can cause the ASMI web server to crash with possible memory corruption and generate an error log; hosted partitions are not affected. The ASMI web interface will restart automatically; however, repeated exploitation could result in a sustained loss of access to the ASMI management interface, resulting in an integrity and availability impact. 2026-08-19 7.6 CVE-2026-16828 IBM--Power Systems Firmware IBM Power Systems Firmware FW950.00 through FW950.H2, OP940.00 through OP940.a1 (Power9), and OP940.00 - OP940.81 (Power HMC) is affected by a vulnerability in host firmware NVRAM parsing. An attacker with root access to a guest partition on an OpenPOWER system can write a specially crafted NVRAM image, causing the host firmware boot stage to crash with possible memory corruption. This condition persists until operator intervention - clearing NVRAM via the service processor - to restore normal operation. This vulnerability only affects OpenPOWER systems; systems running PowerVM are not affected. Successful exploitation results in an integrity and availability impact to the managed system. 2026-08-19 7.3 CVE-2026-17042 IBM--Power Systems Firmware IBM Power Systems Firmware FW1120.00, FW1110.00 through FW1110.30, and FW1060.00 through FW1060.80 is affected by a vulnerability in the interface between the BMC/FSP and the host system. An attacker with service account or root access to the BMC/FSP can access and disrupt host processor state, potentially affecting the managed system and all hosted partitions, resulting in an confidentiality, and availability impact. 2026-08-19 7.9 CVE-2026-17063 IBM--PowerVM Hypervisor IBM PowerVM Hypervisor FW1120.00, FW1110.00 through FW1110.30, FW1060.00 through FW1060.80, and FW950.00 through FW950.H2 is affected by a vulnerability in the service processor mailbox interface. An attacker with authenticated service-level access to the FSP can exploit this vulnerability, allowing arbitrary code to be executed in the host firmware runtime, giving full control over the managed system, resulting in a confidentiality, integrity, and availability impact to the managed system. 2026-08-19 8.2 CVE-2026-16661 IBM--PowerVM Hypervisor IBM PowerVM Hypervisor FW1120.00, FW1110.00 through FW1110.30, FW1060.00 through FW1060.80, and FW950.00 through FW950.H2 is affected by a vulnerability in the service processor mailbox interface. An attacker with authenticated service-level access to the FSP can send a specially crafted mailbox message to read or modify arbitrary regions of Hostboot memory, compromising the host firmware boot stack and the hypervisor subsequently loaded by it. Successful exploitation results in a confidentiality, integrity, and availability impact to the managed system. 2026-08-19 8.2 CVE-2026-16707 IBM--PowerVM Hypervisor IBM PowerVM Hypervisor FW1120.00, FW1110.00 through FW1110.30, FW1060.00 through FW1060.80, and FW950.00 through FW950.H2 is affected by a vulnerability in the PowerVM hypervisor call interface. An attacker with root access to a guest partition can issue a specially crafted hypervisor call to inject an arbitrary amount of data into hypervisor or partition memory, resulting in either a crash causing a full platform re-IPL and terminating all hosted partitions, or corruption of hypervisor or partition memory. The PowerVM hypervisor will restart automatically; however, repeated exploitation could result in a sustained availability impact. Successful exploitation results in an integrity and availability impact to the managed system. 2026-08-19 8.4 CVE-2026-17091 IBM--PowerVM Hypervisor IBM PowerVM Hypervisor FW1120.00, FW1110.00 through FW1110.30, FW1060.00 through FW1060.80, and FW950.00 through FW950.H2 Power Systems Firmware is affected by a vulnerability in partition firmware during network boot. An unauthenticated attacker with access to the same network as a partition performing a network boot can prevent that partition from completing its boot sequence. On partitions where OS secure boot is not enabled, which is the default configuration, the attacker can also substitute the boot image, compromising everything subsequently loaded by that partition. Other partitions and the managed system are not affected. Only partitions actively performing a network boot are affected, resulting in a confidentiality, integrity, and availability impact. 2026-08-19 8.1 CVE-2026-17414 IBM--PowerVM Hypervisor IBM PowerVM Hypervisor FW1120.00, FW1110.00 through FW1110.30, FW1060.00 through FW1060.80, and FW950.00 through FW950.H2 is affected by a vulnerability in the PowerVM hypervisor call interface. An attacker with root access to a guest partition can issue a specially crafted hypervisor call causing a virtual processor to become permanently unresponsive, requiring a full platform re-IPL to restore normal operation. In some cases this may also cause the guest to inject a small amount of data into hypervisor or partition memory with no attacker control over the target location. Successful exploitation results in an integrity and availability impact to the managed system. 2026-08-19 7.3 CVE-2026-17097 IBM--PowerVM Hypervisor IBM PowerVM Hypervisor FW1120.00, FW1110.00 through FW1110.30, FW1060.00 through FW1060.80, and FW950.00 through FW950.H2 Power Systems Firmware is affected by a vulnerability in partition firmware during network boot. An unauthenticated attacker on the same network as a partition undergoing network boot can send a malformed packet, allowing arbitrary code to be executed in the partition firmware and compromising everything subsequently loaded by that partition. Other partitions and the managed system are not affected. Only partitions actively performing a network boot are affected, resulting in a confidentiality, integrity, and availability impact. 2026-08-19 7.5 CVE-2026-18821 IBM--PowerVM Hypervisor IBM PowerVM Hypervisor FW1120.00, FW1110.00 through FW1110.30, and FW1060.00 through FW1060.80 is affected by a vulnerability in host firmware configuration parsing. An attacker with authenticated service-level access to the service processor can write specially crafted configuration data, causing the host firmware boot stack to crash with possible memory corruption during system initialisation, resulting in an integrity and availability impact to the managed system. 2026-08-19 7.3 CVE-2026-18871 ICEcoder--ICEcoder ICEcoder 8.1 contains an unauthenticated remote code execution vulnerability that allows unauthenticated attackers to execute arbitrary OS commands by chaining an authentication bypass, CSRF validation bypass, and unsanitized command execution. Attackers can send a single HTTP POST request to the terminal endpoint with a password parameter to bypass authentication, a non-empty csrf parameter to skip CSRF validation, and an arbitrary command string passed directly to proc_open() to achieve remote code execution as the web-server user. 2026-08-19 9.8 CVE-2026-63722 indilib--indi INDI (Instrument Neutral Distributed Interface) indiserver through 2.2.4.2, fixed in commit 96bbd7f, contains a stack buffer overflow vulnerability that allows unauthenticated remote attackers to crash the daemon by sending malformed XML with mismatched tags whose names exceed 1024 bytes. Attackers can send a single TCP packet on port 7624 with mismatched XML tags to trigger an unbounded sprintf() write into a fixed 1024-byte stack buffer in MsgQueue.cpp, terminating the daemon and disrupting all active client and driver sessions. 2026-08-17 7.5 CVE-2026-71979 indithemes--IT Residence Subscriber Arbitrary File Upload in IT Residence defaultAtts to determine CDATA status. A remote unauthenticated attacker can supply a single well-formed XML document of a few megabytes to an application parsing untrusted XML to cause excessive CPU consumption, resulting in denial of service without requiring authentication, external entity resolution, or non-default parser options. 2026-08-18 7.5 CVE-2026-66046 libexpat--libexpat Expat through 2.8.3 contains an out-of-bounds read vulnerability that allows attackers to trigger memory corruption by processing XML with external entity parsers created via XML_ExternalEntityParserCreate. A struct size mismatch between ELEMENT_TYPE members causes storeAtts to read the attIndex member past allocated memory boundaries, resulting in failure to normalize whitespace in non-CDATA attributes or a wild pointer dereference causing a segfault. This vulnerability was introduced by the fix for CVE-2026-66046. 2026-08-20 7.5 CVE-2026-76641 libfuse--sshfs SSHFS is a network filesystem client for connecting to SSH servers. Prior to version 3.7.6, a rogue SFTP server can return absolute symlink targets or relative targets containing parent-directory components that SSHFS passes through FUSE for resolution by the client kernel against the local filesystem. The documented transform_symlinks mitigation does not contain relative targets because transform_symlink() returns early at sshfs.c:2181, while sshfs_readlink() at sshfs.c:2234 to sshfs.c:2236 otherwise copies the server-supplied link target to the kernel. A victim or victim-side tool that follows such a link through ordinary operations such as cp, rsync, backup tooling, or an editor can disclose readable local files back to the server or write server-controlled content to writable local files, potentially including startup or scheduled-task files. This issue is fixed in version 3.7.6. 2026-08-19 9.3 CVE-2026-47187 libfuse--sshfs SSHFS is a network filesystem client for connecting to SSH servers. From version 1.4 until 3.7.6, SSHFS accepts a bracketed mount source such as [-oProxyCommand=CMD]:/path and find_base_path() removes the brackets, leaving a host value that begins with - and is passed directly to ssh as a command-line argument. When a caller also supplies a path-valued sftp_server, ssh treats the normalized host as an option and the server path as its destination, causing an injected ProxyCommand to execute locally before any connection or authentication succeeds. The attack requires a caller or wrapper that passes an attacker-controlled mount source to SSHFS with the required sftp_server configuration and results in arbitrary command execution as the user running SSHFS. This issue is fixed in version 3.7.6. 2026-08-19 7 CVE-2026-48711 libgit2--libgit2 libgit2 is a portable C implementation of the Git core methods provided as a linkable library with a solid API, allowing to build Git functionality into your application. Prior to 1.8.6 and 1.9.5, libgit2 performs a fixed-size strncmp in set_data in src/libgit2/transports/smart_pkt.c without first verifying that the smart-protocol pkt-line capability buffer contains 14 bytes. A malicious Git server can make bytes after the pkt-line complete object-format=, causing format_str to advance beyond the pkt-line and the following memchr length calculation to underflow. The resulting heap out-of-bounds walk can crash a client during the first refs-advertisement packet over HTTP, HTTPS, SSH, or the Git protocol. This issue is fixed in versions 1.8.6 and 1.9.5. 2026-08-20 7.5 CVE-2026-53587 LibVNC--libvncserver LibVNCClient is a library for easy implementation of a VNC client. In versions 0.9.12 through 0.9.15, a malicious (or man-in-the-middle) VNC server can force a connecting `libvncclient` to write attacker-controlled data past the end of its framebuffer. This is an out-of-bounds heap write with attacker-controlled length, contents, and offset. It needs no authentication (the attacker is the server), works in a default build with default settings, and fires from a single `FramebufferUpdate` the moment the victim connects. It crashes any client unconditionally (denial of service); we also demonstrated it overwriting an application callback pointer and redirecting execution to attacker-chosen code (code execution) under the default configuration. Commit 540332be3e0acc566fa64da6f1b4680c72c724dd patches the issue. 2026-08-21 8.8 CVE-2026-50538 liedekef--Events Made Easy The Events Made Easy plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 3.2.5 via the eme_single_event_page_template function. This makes it possible for authenticated attackers, with contributor-level access and above, to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included. The stored traversal payload is triggered passively when any visitor loads the affected single-event page, meaning post-submission execution does not require additional attacker interaction. 2026-08-20 7.5 CVE-2026-75963 liftoff-sr--CIPster A security flaw has been discovered in liftoff-sr CIPster 1802525be27d33e19a9a83c163e331a1d13b1892. The impacted element is the function CipAttribute::GetAttrData/CipAttribute::SetAttrData of the file ciptypes.h of the component Generic Attribute Logic. Performing a manipulation results in memory corruption. It is possible to initiate the attack remotely. The exploit has been released to the public and may be used for attacks. The patch is named e745d9d4a8ca3a13689066983a1269fe1e567674. It is suggested to install a patch to address this issue. 2026-08-20 7.3 CVE-2026-76987 Linuxfabrik--monitoring-plugins linuxfabrik-lib provides Python modules for database access, caching, shell execution, and API integrations, and Linuxfabrik Monitoring Plugins uses those modules to run external monitoring commands. From the earliest affected releases until linuxfabrik-lib 5.0.0 and Linuxfabrik Monitoring Plugins 6.0.0, check plugins embedded user-controlled values in command strings passed to lib.shell.shell_exec(), which split strings at pipe characters and executed the resulting commands. In check-plugins/restic-check/restic-check, the --repo parameter could inject a pipe-delimited command into a constructed restic invocation, and sudo-authorized execution allowed a compromised nagios or icinga account to run that command as root. The shared library also accepted command strings and a shell parameter, while numerous plugins constructed external commands from attacker-influenced arguments. The fixes require argv lists, always use shell=False, remove pipe splitting, and reject option-like positional values through lib.shell.safe_cli_value(). These issues are fixed in linuxfabrik-lib 5.0.0 and Linuxfabrik Monitoring Plugins 6.0.0. 2026-08-18 7.8 CVE-2026-55426 logto-io--logto Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 1.41.0, Logto's email subaddressing blocklist in packages/core/src/libraries/sign-in-experience/email-blocklist-policy.ts used the attacker-controlled domain from email input to construct subaddressingRegex when blockSubaddressing was enabled. The permissive emailRegEx accepted multiple at signs and regular expression metacharacters, and POST /api/experience/verification/verification-code could therefore cause catastrophic backtracking in subaddressingRegex.test(email). The resulting event-loop stall could make authentication, token issuance, SSO, and the administrative console unavailable. This issue is fixed in version 1.41.0. 2026-08-19 7.5 CVE-2026-62317 louislam--dockge Dockge validates a stack name only on the write path. In backend/stack.ts the allow-list check in validate(), which requires the name to match ^[a-z0-9_-]+$, is reached from save() alone, while the path getter returns path.join(this.server.stacksDir, this.name) and Stack.getStack builds path.join(server.stacksDir, stackName) with no check. The socket handlers in backend/agent-socket-handlers/docker-socket-handler.ts confirm the caller is logged in and that the name is a string, then pass it straight to Stack.getStack, so a name containing traversal sequences resolves outside the managed stacks directory. An authenticated user can therefore read the composeENV and composeYAML values of any directory the server process can reach, which discloses the secrets in that directory's .env or Compose file, and can invoke delete(), which runs docker compose down and then fsAsync.rm on the traversed path with recursive and force set, removing that directory. Disclosure is limited to files named .env or an accepted Compose filename, and deletion requires the target directory to hold a valid Compose file so that docker compose down exits successfully. Dockge commonly runs as root with access to the Docker socket, so the reachable set includes unrelated applications on the host. Instances configured with disableAuth, a supported option that logs the caller in as admin automatically, expose both operations without authentication. 2026-08-20 8.8 CVE-2026-73040 lukeseager--WordPress Persistent Login Subscriber SQL Injection in WordPress Persistent Login

Read more »

A list of macOS versions in order by year
Every Mac runs on macOS, but the system has changed names, version numbers, and designs several times since it first came out in 2001. Whether you’re trying to see which version your Mac is using, check if it’s eligible for an upgrade, or track down an older release, it’s easier when you can see how […] The post first appeared on The Mac Security Blog.

Read more »

A list of macOS versions in order by year
Every Mac runs on macOS, but the system has changed names, version numbers, and designs several times since it first came out in 2001. Whether you’re trying to see which version your Mac is using, check if it’s eligible for an upgrade, or track down an older release, it’s easier when you can see how […] The post first appeared on The Mac Security Blog.

Read more »

Can Macs get viruses? How to protect your Mac
Many Mac owners believe malware is only a Windows problem. While macOS includes strong built-in security protections, Macs can still be infected with viruses, Trojans, ransomware, spyware, adware, and other malware. Understanding how these threats work is the first step to avoiding them. This guide explains whether Macs can get viruses, how infections happen, the […] The post first appeared on The Mac Security Blog.

Read more »

Can Macs get viruses? How to protect your Mac
Many Mac owners believe malware is only a Windows problem. While macOS includes strong built-in security protections, Macs can still be infected with viruses, Trojans, ransomware, spyware, adware, and other malware. Understanding how these threats work is the first step to avoiding them. This guide explains whether Macs can get viruses, how infections happen, the […] The post first appeared on The Mac Security Blog.

Read more »

How to clear cookies on Mac
Tutorial about browser cookies and how to manage them in every major browser on Mac and iOS. This guide also explains what it means to delete your cookies—and why it might be a good idea to do so. The post first appeared on The Mac Security Blog.

Read more »

How to clear cookies on Mac
Tutorial about browser cookies and how to manage them in every major browser on Mac and iOS. This guide also explains what it means to delete your cookies—and why it might be a good idea to do so. The post first appeared on The Mac Security Blog.

Read more »

What are trackers on Safari? How to stop websites from tracking you
Open Safari’s Privacy Report and you might see a line telling you how many trackers it’s prevented from profiling you in the last seven days. It’s natural to wonder if your Mac’s been infected, or if someone’s watching what you do online, but it’s almost always neither. What it means is that Safari has spotted […] The post first appeared on The Mac Security Blog.

Read more »

What are trackers on Safari? How to stop websites from tracking you
Open Safari’s Privacy Report and you might see a line telling you how many trackers it’s prevented from profiling you in the last seven days. It’s natural to wonder if your Mac’s been infected, or if someone’s watching what you do online, but it’s almost always neither. What it means is that Safari has spotted […] The post first appeared on The Mac Security Blog.

Read more »

Who’s Tracking You? Use This New Service to Find Out
It can be daunting to determine who's responsible for showing ads on the websites we visit, or who's harvesting data from the mobile apps we use every day. That information is already semi-public, but it is not easily parsed and traditionally much of it has remained walled away in the hands of large advertising platforms. Not anymore: A powerful and free new service called DecryptAds scrapes and correlates this adtech data and makes it simple to quickly learn a great deal about the entities that are tracking you.

Read more »

Microsoft Plugs Nearly 400 Security Holes
Microsoft today released updates to remedy at least 398 security vulnerabilities in its Windows operating systems and supported software, including one weakness that is already being actively exploited and two others that were publicly detailed prior to today.

Read more »

Canadian Man Pleads Guilty in Snowflake Extortions
A 26-year-old Canadian man once described as one of the most consequential cybercrime threat actors of 2024 has pleaded guilty to computer fraud and conspiracy to hack and extort more than 165 organizations that used the cloud data storage provider Snowflake. Connor Riley Moucka, of Kitchener, Ontario, also admitted to stealing call and text history records of more than 100 million AT&T customers.

Read more »

Vulnerability Summary for the Week of July 27, 2026
High Vulnerabilities PrimaryVendor -- Product Description Published CVSS Score Source Info @fastify/rate-limit--@fastify/rate-limit @fastify/rate-limit before 11.2.0 keys rate-limit buckets by the verbatim client IP string returned from request.ip. Because a single IPv6 client can control a large address range (a /64 holds 2^64 distinct addresses) and the same address has multiple valid textual representations, an IPv6 capable client can defeat the rate-limit boundary by rotating addresses or by rewriting the same address in different forms. Applications that use @fastify/rate-limit to protect endpoints such as authentication, password reset, OTP delivery, or expensive API calls can be bypassed by IPv6 clients behind a proxy that surfaces IPv6 to the origin when trustProxy is enabled. The issue is fixed in @fastify/rate-limit 11.2.0, where the default key generator normalizes IPv6 addresses to their canonical form, collapses IPv4 mapped IPv6 to IPv4, and applies a configurable prefix mask (default /64) via a new ipv6Subnet option. 2026-07-29 7.3 CVE-2026-15144 acacode--swagger-typescript-api swagger-typescript-api generates API clients for Fetch or Axios from an OpenAPI Specification. Prior to 13.12.2, templates/base/http-clients/axios-http-client.ejs interpolates servers[0].url from src/code-gen-process.ts into the HttpClient constructor without escaping, allowing an attacker-controlled OpenAPI spec to inject code that executes when new HttpClient() or new Api() is constructed. This issue is fixed in version 13.12.2. 2026-07-29 8.3 CVE-2026-54661 acacode--swagger-typescript-api swagger-typescript-api generates API clients for Fetch or Axios from OpenAPI specifications. Prior to 13.12.2, src/code-gen-process.ts createApiConfig copies servers[0].url into apiConfig.baseUrl, and templates/base/http-clients/fetch-http-client.ejs interpolates apiConfig.baseUrl into the generated HttpClient baseUrl field without escaping, allowing an attacker-controlled OpenAPI spec to inject TypeScript static field code that executes when the generated fetch client module is imported. This issue is fixed in version 13.12.2. 2026-07-29 8.3 CVE-2026-54662 acacode--swagger-typescript-api swagger-typescript-api generates API clients for Fetch or Axios from an OpenAPI Specification. Prior to 13.12.2, src/schema-parser/base-schema-parsers/enum.ts passes components.schemas.*.enum[i] values to Ts.StringValue in src/configuration.ts without escaping before templates/base/enum-data-contract.ejs renders TypeScript enum declarations, allowing an attacker-controlled OpenAPI spec to inject code that executes when the generated module is imported. This issue is fixed in version 13.12.2. 2026-07-29 8.3 CVE-2026-54664 acacode--swagger-typescript-api swagger-typescript-api generates API clients for Fetch or Axios from an OpenAPI Specification. Prior to 13.12.2, src/schema-routes/schema-routes.ts passes OpenAPI path keys through parseRouteName to templates/default/procedure-call.ejs and templates/modular/procedure-call.ejs without escaping JavaScript template literal interpolation, allowing an attacker-controlled path containing ${...} to execute when the generated method is called. This issue is fixed in version 13.12.2. 2026-07-29 8.3 CVE-2026-54666 acacode--swagger-typescript-api swagger-typescript-api generates API clients for Fetch or Axios from OpenAPI specifications. Prior to 13.12.2, src/resolved-swagger-schema.ts getRemoteRequestHeaders forwards --authorizationToken to every URL fetched by fetchRemoteSchemaDocument while warmUpRemoteSchemasCache resolves external $ref URLs, allowing an attacker-controlled OpenAPI spec to exfiltrate the developer or CI bearer token to a cross-origin endpoint. This issue is fixed in version 13.12.2. 2026-07-29 7.4 CVE-2026-54660 acowebs--Dynamic Pricing With Discount Rules for WooCommerce Unauthenticated Cross Site Scripting (XSS) in Dynamic Pricing With Discount Rules for WooCommerce = 1.4.0-beta.27 through = 1.7.0-beta.0 through sk) inside smc_cdc_msg_recv(). No reference is held across the lock release. The only reference pinning the socket while the connection is discoverable in the link group is taken in smc_lgr_register_conn() (sock_hold) and dropped in __smc_lgr_unregister_conn() (sock_put), both under conns_lock. Once the handler drops conns_lock, a concurrent close() - > smc_release() - > smc_conn_free() - > smc_lgr_unregister_conn() can drop that reference and free the smc_sock, so the handler's later sock_hold() runs on freed memory: WARNING: lib/refcount.c:25 at refcount_warn_saturate Workqueue: rxe_wq do_work refcount_warn_saturate (lib/refcount.c:25) smc_cdc_msg_recv (net/smc/smc_cdc.c:430) smc_cdc_rx_handler (net/smc/smc_cdc.c:502) smc_wr_rx_tasklet_fn (net/smc/smc_wr.c:445) tasklet_action_common (kernel/softirq.c:938) handle_softirqs (kernel/softirq.c:622) Kernel panic - not syncing: panic_on_warn set Only SMC-R is affected. The SMC-D receive tasklet is stopped by tasklet_kill(&conn- >rx_tsklet) in smc_conn_free() before the connection is unregistered, so it cannot run concurrently with the free. Take the socket reference while still holding conns_lock, so the registration reference can no longer be the last one, and drop it once the handler is done. 2026-07-27 9.8 CVE-2026-64541 Linux--Linux In the Linux kernel, the following vulnerability has been resolved: sctp: validate STALE_COOKIE cause length before reading staleness When an ERROR chunk with a STALE_COOKIE cause is received in the COOKIE_ECHOED state, sctp_sf_do_5_2_6_stale() reads the 4-byte Measure of Staleness that follows the cause header: err = (struct sctp_errhdr *)(chunk- >skb- >data); stale = ntohl(*(__be32 *)((u8 *)err + sizeof(*err))); err is the first cause in the chunk, not the STALE_COOKIE cause that caused the dispatch, and nothing guarantees the staleness field is present. sctp_walk_errors() only requires a cause to be as long as the 4-byte header, so for a STALE_COOKIE cause of length 4 the read runs past the cause, and for a minimal ERROR chunk past skb- >tail. The value is echoed to the peer in the Cookie Preservative of the reply INIT, leaking uninitialized memory. sctp_sf_cookie_echoed_err() already walks to the STALE_COOKIE cause, so check its length there and pass it to sctp_sf_do_5_2_6_stale(), which reads that cause instead of the first one. A STALE_COOKIE cause too short to hold the staleness field is discarded. The read is reachable by any peer that can drive an association into COOKIE_ECHOED, including an unprivileged process using a raw SCTP socket in a user and network namespace. 2026-07-27 9.1 CVE-2026-64551 Linux--Linux In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs: fix OOB reads in is_ap_in_tkip() IE loop The loop in is_ap_in_tkip() iterates over IEs without verifying that enough bytes remain before dereferencing the IE header or its payload: - pIE- >element_id and pIE- >length are read without checking that i + sizeof(*pIE) data + 12, which requires pIE- >length >= 16. For WLAN_EID_RSN it compares pIE- >data + 8, requiring pIE- >length >= 12. Neither requirement is checked. Add the missing IE header and payload bounds checks and guard each data access with an explicit pIE- >length minimum, matching the pattern established in update_beacon_info(). 2026-07-27 8.1 CVE-2026-64536 Linux--Linux In the Linux kernel, the following vulnerability has been resolved: usbnet: gl620a: fix out-of-bounds read in genelink_rx_fixup() genelink_rx_fixup() splits an aggregated RX frame into its individual packets, using a per-packet length taken from device-supplied data. That length is only bounded by GL_MAX_PACKET_LEN (1514); it is never compared against how many bytes were actually received. A malicious GeneLink (GL620A) device can therefore send a short URB whose header claims packet_count > 1 and a first packet of up to 1514 bytes. skb_put_data(gl_skb, packet- >packet_data, size); then copies past the end of the receive buffer and hands the adjacent slab contents up the network stack, an out-of-bounds read that leaks kernel heap. No privilege is required: the path runs in the usbnet RX softirq as soon as the interface is up. BUG: KASAN: slab-out-of-bounds in genelink_rx_fixup (drivers/net/usb/gl620a.c:112) Read of size 1514 at addr ffff888011309708 by task ksoftirqd/0/14 Call Trace: ... __asan_memcpy (mm/kasan/shadow.c:105) genelink_rx_fixup (include/linux/skbuff.h:2814 drivers/net/usb/gl620a.c:112) usbnet_bh (drivers/net/usb/usbnet.c:572 drivers/net/usb/usbnet.c:1589) process_one_work (kernel/workqueue.c:3322) bh_worker (kernel/workqueue.c:3405) tasklet_action (kernel/softirq.c:965) handle_softirqs (kernel/softirq.c:622) run_ksoftirqd (kernel/softirq.c:1076) ... skb_pull() already verifies that the requested length fits the buffer and returns NULL otherwise. Move it ahead of the copy and check its result, so a packet that overruns the received data is rejected before it is read. Well-formed frames, whose packets are fully present, are unaffected. 2026-07-27 8.1 CVE-2026-64540 Linux--Linux In the Linux kernel, the following vulnerability has been resolved: net: usb: net1080: validate packet_len before pad-byte access in rx_fixup For an even packet_len, net1080_rx_fixup() reads the pad byte at skb- >data[packet_len] before the skb- >len != packet_len check further down, and packet_len is only bounded against NC_MAX_PACKET. A malicious NetChip 1080 device can send a short frame advertising a large even packet_len (e.g. 0x4000), so the pad-byte read lands past the end of the skb: BUG: KASAN: slab-out-of-bounds in net1080_rx_fixup Read of size 1 at addr ffff8880106c83c6 by task ksoftirqd/0/14 ... net1080_rx_fixup (drivers/net/usb/net1080.c:384) usbnet_bh (drivers/net/usb/usbnet.c:1589) process_one_work (kernel/workqueue.c:3322) bh_worker (kernel/workqueue.c:3708) tasklet_action (kernel/softirq.c:965) handle_softirqs (kernel/softirq.c:622) ... Reject the frame when packet_len >= skb- >len before reading. 2026-07-27 8.1 CVE-2026-64547 Linux--Linux In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: reject overflowing copy + len in bpf_msg_push_data() When the scatterlist ring is full or nearly full, bpf_msg_push_data() enters a copy fallback path and computes copy + len for the page allocation size. Since len comes from BPF with arg3_type = ARG_ANYTHING and both are u32, a crafted len can wrap the sum to a small value, causing an undersized allocation followed by an out-of-bounds memcpy. BUG: unable to handle page fault for address: ffffed104089a402 Oops: Oops: 0000 [#1] SMP KASAN NOPTI Call Trace: __asan_memcpy (mm/kasan/shadow.c:105) bpf_msg_push_data (net/core/filter.c:2852 net/core/filter.c:2788) bpf_prog_9ed8b5711920a7d7+0x2e/0x36 sk_psock_msg_verdict (net/core/skmsg.c:934) tcp_bpf_sendmsg (net/ipv4/tcp_bpf.c:421 net/ipv4/tcp_bpf.c:584) __sys_sendto (net/socket.c:2206) do_syscall_64 (arch/x86/entry/syscall_64.c:94) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130) Add an overflow check before the allocation. 2026-07-27 8.4 CVE-2026-64548 Linux--Linux In the Linux kernel, the following vulnerability has been resolved: virtio-net: fix len check in receive_big() receive_big() bounds the device-announced length by (big_packets_num_skbfrags + 1) * PAGE_SIZE. That is still too loose: add_recvbuf_big() sets sg[1] to start at offset sizeof(struct padded_vnet_hdr) into the first page, so the chain actually carries hdr_len + (PAGE_SIZE - sizeof(padded_vnet_hdr)) + big_packets_num_skbfrags * PAGE_SIZE bytes -- 20 bytes less than the check allows for the common hdr_len == 12 case. A malicious virtio backend can announce a len in that gap. page_to_skb() then walks one frag past the page chain, storing a NULL page- >private into skb_shinfo()- >frags[MAX_SKB_FRAGS], which is both an out-of-bounds write past the static frag array and a NULL frag handed up the rx path. Bound len by the size add_recvbuf_big() actually advertised. 2026-07-27 8.4 CVE-2026-64552 Linux--Linux In the Linux kernel, the following vulnerability has been resolved: netfilter: bridge: fix stale prevhdr pointer in br_ip6_fragment() br_ip6_fragment() gets prevhdr, a pointer into the skb head, from ip6_find_1stfragopt(), then calls skb_checksum_help(). For a cloned skb skb_checksum_help() reallocates the head via pskb_expand_head(), leaving prevhdr dangling. It is later dereferenced in ip6_frag_next(), causing a use-after-free write. Save prevhdr's offset before skb_checksum_help() and recompute it after, like commit ef0efcd3bd3f ("ipv6: Fix dangling pointer when ipv6 fragment"). BUG: KASAN: slab-use-after-free in ip6_frag_next (net/ipv6/ip6_output.c:857) Write of size 1 at addr ffff888013ff5016 by task exploit/141 Call Trace: ... kasan_report (mm/kasan/report.c:595) ip6_frag_next (net/ipv6/ip6_output.c:857) br_ip6_fragment (net/ipv6/netfilter.c:212) nf_ct_bridge_post (net/bridge/netfilter/nf_conntrack_bridge.c:407) nf_hook_slow (net/netfilter/core.c:619) br_forward_finish (net/bridge/br_forward.c:66) __br_forward (net/bridge/br_forward.c:115) maybe_deliver (net/bridge/br_forward.c:191) br_flood (net/bridge/br_forward.c:245) br_handle_frame_finish (net/bridge/br_input.c:229) br_handle_frame (net/bridge/br_input.c:442) ... packet_sendmsg (net/packet/af_packet.c:3114) ... do_syscall_64 (arch/x86/entry/syscall_64.c:94) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121) Kernel panic - not syncing: Fatal exception in interrupt 2026-07-27 8.8 CVE-2026-64554 Linux--Linux In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: nv: Fix SPSR_EL2 restore in kvm_hyp_handle_mops() kvm_hyp_handle_mops() resets the single-step state machine as part of rewinding state for a MOPS exception by modifying vcpu_cpsr() and writing the result directly into hardware. In the case of nested virtualization, vcpu_cpsr() is a synthetic value such that the rest of KVM can deal with vEL2 cleanly. That means the value requires translation before being written into hardware, which is unfortunately missing from the MOPS handler. Fix it by directly modifying SPSR_EL2 and avoiding the synthetic state altogether, which will be resynchronized on the next 'full' exit back to KVM. 2026-07-27 8.8 CVE-2026-64555 Linux--Linux In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix use-after-free in l2cap_sock_new_connection_cb() l2cap_sock_new_connection_cb() returned l2cap_pi(sk)- >chan after release_sock(parent). Once the parent lock is dropped the newly enqueued child socket sk is reachable via the accept queue, so another task can accept and free it before the callback dereferences sk, resulting in a use-after-free. Rework the - >new_connection() op so the core, rather than the callback, owns the child channel's lifetime. The op now receives a pre-allocated new_chan and returns an errno instead of allocating and returning a channel. l2cap_new_connection() allocates the child channel and links it into the conn list via __l2cap_chan_add() before invoking the callback, so the conn-list reference keeps the channel alive once release_sock(parent) exposes the socket to other tasks. Channel configuration that was duplicated in l2cap_sock_init() and the various new_connection callbacks is consolidated into l2cap_chan_set_defaults(), which now inherits from the parent channel when one is supplied. 2026-07-29 8.8 CVE-2026-64557 Linux--Linux In the Linux kernel, the following vulnerability has been resolved: net: openvswitch: reject oversized nested action attrs Open vSwitch stores generated flow actions as nlattrs, whose nla_len field is u16. Commit a1e64addf3ff ("net: openvswitch: remove misbehaving actions length check") allowed the total sw_flow_actions stream to grow beyond 64 KiB, which is valid, but also removed the last guard preventing a generated nested action attribute from exceeding U16_MAX. An oversized generated container can thus be closed with a truncated nla_len. A later dump or teardown then walks a structurally different stream than the one that was validated. In particular, an oversized nested CLONE/CT action may cause subsequent bytes in the generated stream to be interpreted as independent actions. Keep the larger total-action-stream behavior, but make nested action close reject generated containers that do not fit in nla_len, and return the error through all callers. For recursive SAMPLE, CLONE, DEC_TTL, and CHECK_PKT_LEN builders, trim resource-owning action-list tails in reverse construction order before discarding failed wrappers, so resources copied into the rejected tails are released before the wrappers are removed. Most failed outer wrappers are discarded by truncating actions_len after child resources have been released. CHECK_PKT_LEN also trims its parent after branch resources are gone. SET/TUNNEL close failures unwind their known tun_dst ownership directly, and SET_TO_MASKED has no external ownership and truncates on close failure. 2026-07-27 7.8 CVE-2026-64531 Linux--Linux In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: bound NTFS_DE view.data_off in UpdateRecordData{Root,Allocation} In do_action()'s UpdateRecordDataRoot (fslog.c:3489) and UpdateRecordDataAllocation (fslog.c:3697) cases, the memmove destination is `Add2Ptr(e, le16_to_cpu(e- >view.data_off))`, where e- >view.data_off comes from an on-disk NTFS_DE inside an INDEX_ROOT or INDEX_BUFFER. Neither case validates view.data_off + dlen against e- >size; the existing check_if_index_root / check_if_alloc_index helpers walk the entry chain and validate the entry's offset, but not its internal view fields. The neighbouring read sites (e.g., fs/ntfs3/index.c when iterating view entries) check view.data_off + view.data_size size. Apply the same bound at the two memmove sites. Reproduced under UML+KASAN on mainline 8d90b09e6741 via pr_warn-only probe instrumentation: with view.data_off forced to 0xFFFC, the memmove writes 32 bytes past the end of the NTFS_DE. This is similar in shape to Pavitra Jha's 2026-05-02 patch "fs/ntfs3: prevent oob in case UpdateRecordDataRoot" () which proposes calling ntfs3_bad_de_range(); that helper does not exist in mainline. This patch uses inline checks. 2026-07-27 7.8 CVE-2026-64532 Linux--Linux In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: validate lcns_follow in log_replay conversion log_replay() converts DIR_PAGE_ENTRY_32 records into DIR_PAGE_ENTRY records when replaying version 0 restart tables. During this conversion, the memmove() length is derived directly from the on-disk lcns_follow field: memmove(&dp- >vcn, &dp0- >vcn_low, 2 * sizeof(u64) + le32_to_cpu(dp- >lcns_follow) * sizeof(u64)); check_rstbl() validates restart table structure, but does not constrain per-entry lcns_follow values relative to the entry size. A malformed filesystem image can provide an oversized lcns_follow value, causing the conversion memmove() to access memory beyond the bounds of the allocated restart table buffer. The same field is later used to bound iteration over page_lcns[], so validating lcns_follow during conversion also prevents downstream out-of-bounds access from the same malformed metadata. Compute the maximum valid lcns_follow from the already-validated restart table entry size and reject entries that exceed this bound. Reuse the existing t16/t32 scratch variables already declared in log_replay() to avoid introducing new declarations. [almaz.alexandrovich@paragon-software.com: fixed the conflicts] 2026-07-27 7.8 CVE-2026-64533 Linux--Linux In the Linux kernel, the following vulnerability has been resolved: Bluetooth: eir: Fix stack OOB write when prepending the Flags AD eir_create_adv_data() builds the advertising data into a fixed-size buffer ("size", 31 for the legacy path). It may prepend a 3-byte "Flags" AD structure (LE_AD_NO_BREDR on an LE-only controller) and then copies the per-instance data without checking that it still fits: memcpy(ptr, adv- >adv_data, adv- >adv_data_len); tlv_data_max_len() only reserves those 3 bytes when the user-supplied flags carry a managed-flags bit, so an instance added with flags == 0 is accepted with adv_data_len up to the full buffer. At advertise time the flags are still prepended, and the memcpy() writes 3 + adv_data_len bytes into the size-byte buffer: BUG: KASAN: stack-out-of-bounds in eir_create_adv_data (net/bluetooth/eir.c:301) Write of size 31 at addr ffff88800a547bdc by task kworker/u9:0/65 Workqueue: hci0 hci_cmd_sync_work __asan_memcpy (mm/kasan/shadow.c:106) eir_create_adv_data (net/bluetooth/eir.c:301) hci_update_adv_data_sync (net/bluetooth/hci_sync.c:1310) hci_schedule_adv_instance_sync (net/bluetooth/hci_sync.c:1817) hci_cmd_sync_work (net/bluetooth/hci_sync.c:332) This frame has 1 object: [32, 64) 'cp' The "Flags" structure is added by the kernel, not requested by userspace, so only prepend it when it fits together with the instance advertising data; when there is no room for both, drop the flags rather than the user-provided data. Reachable by a local user with CAP_NET_ADMIN owning an LE-only controller on the legacy advertising path. 2026-07-27 7.8 CVE-2026-64539 Linux--Linux In the Linux kernel, the following vulnerability has been resolved: tipc: fix use-after-free of the discoverer in tipc_disc_rcv() bearer_disable() frees b- >disc with tipc_disc_delete()'s plain kfree(), but tipc_disc_rcv() still dereferences b- >disc in RX softirq under rcu_read_lock() (tipc_udp_recv - > tipc_rcv - > tipc_disc_rcv). L2 bearers are safe thanks to the synchronize_net() in tipc_disable_l2_media(), but the UDP bearer defers that call to the cleanup_bearer() workqueue, so the discoverer is freed with no grace period: BUG: KASAN: slab-use-after-free in tipc_disc_rcv (net/tipc/discover.c:149) Read of size 8 at addr ffff88802348b728 by task poc_tipc/184 tipc_disc_rcv (net/tipc/discover.c:149) tipc_rcv (net/tipc/node.c:2126) tipc_udp_recv (net/tipc/udp_media.c:391) udp_rcv (net/ipv4/udp.c:2643) ip_local_deliver_finish (net/ipv4/ip_input.c:241) Freed by task 181: kfree (mm/slub.c:6565) bearer_disable (net/tipc/bearer.c:418) tipc_nl_bearer_disable (net/tipc/bearer.c:1001) The bearer is freed with kfree_rcu(); free the discoverer the same way. Add an rcu_head to struct tipc_discoverer and free it and its skb from an RCU callback. Because the RCU callback (tipc_disc_free_rcu) lives in module text, a call_rcu() that is still pending when the tipc module is unloaded would invoke a freed function. Add an rcu_barrier() to tipc_exit() after the bearer subsystem has been torn down, so all pending discoverer callbacks have run before the module text goes away. Reachable from an unprivileged user namespace: the TIPCv2 genl family is netnsok and its bearer commands have no GENL_ADMIN_PERM. Needs CONFIG_TIPC and CONFIG_TIPC_MEDIA_UDP. 2026-07-27 7.8 CVE-2026-64543 Linux--Linux In the Linux kernel, the following vulnerability has been resolved: net, bpf: check master for NULL in xdp_master_redirect() xdp_master_redirect() dereferences the result of netdev_master_upper_dev_get_rcu() without a NULL check, but that helper returns NULL when the receiving device has no upper-master adjacency. The reach guard only checks netif_is_bond_slave(). On bond slave release bond_upper_dev_unlink() drops the upper-master adjacency before clearing IFF_SLAVE, so an XDP_TX reaching xdp_master_redirect() in that window still passes netif_is_bond_slave() while master is already NULL, and faults on master- >flags at offset 0xb0: BUG: kernel NULL pointer dereference, address: 00000000000000b0 RIP: 0010:xdp_master_redirect (net/core/filter.c:4432) Call Trace: xdp_master_redirect (net/core/filter.c:4432) bpf_prog_run_generic_xdp (include/net/xdp.h:700) do_xdp_generic (net/core/dev.c:5608) __netif_receive_skb_one_core (net/core/dev.c:6204) process_backlog (net/core/dev.c:6319) __napi_poll (net/core/dev.c:7729) net_rx_action (net/core/dev.c:7792) handle_softirqs (kernel/softirq.c:622) __dev_queue_xmit (include/linux/bottom_half.h:33) packet_sendmsg (net/packet/af_packet.c:3082) __sys_sendto (net/socket.c:2252) Kernel panic - not syncing: Fatal exception in interrupt The missing check dates back to the original code; commit 1921f91298d1 ("net, bpf: fix null-ptr-deref in xdp_master_redirect() for down master") later added the master- >flags read where the fault now lands but kept the unconditional deref. Check master for NULL before use; a NULL master is treated the same as one that is not up. 2026-07-27 7.5 CVE-2026-64545 Linux--Linux In the Linux kernel, the following vulnerability has been resolved: drm/edid: fix OOB read in drm_parse_tiled_block() drm_parse_tiled_block() casts the DisplayID block to a struct displayid_tiled_block and reads the full fixed layout up to tile- >topology_id[7] without checking block- >num_bytes. The DisplayID iterator only validates the declared payload length, so a crafted EDID can advertise a tiled-display block (tag DATA_BLOCK_TILED_DISPLAY, or DATA_BLOCK_2_TILED_DISPLAY_TOPOLOGY for v2.0) with a small num_bytes at the end of a DisplayID extension. The read then runs past the end of the exact-sized kmemdup()'d EDID allocation, a heap out-of-bounds read. Reject blocks shorter than the spec's 22-byte tiled payload before reading the fixed struct, as drm_parse_vesa_mso_data() already does. BUG: KASAN: slab-out-of-bounds in drm_edid_connector_update Read of size 2 at addr ffff888010077700 by task exploit/147 dump_stack_lvl (lib/dump_stack.c:94 ...) print_report (mm/kasan/report.c:378 ...) kasan_report (mm/kasan/report.c:595) drm_edid_connector_update (drivers/gpu/drm/drm_edid.c:7581) bochs_connector_helper_get_modes (drivers/gpu/drm/tiny/bochs.c:574) drm_helper_probe_single_connector_modes (drivers/gpu/drm/drm_probe_helper.c:426) status_store (drivers/gpu/drm/drm_sysfs.c:219) ... vfs_write (fs/read_write.c:595 fs/read_write.c:688) ksys_write (fs/read_write.c:740) 2026-07-27 7.1 CVE-2026-64546 Linux--Linux In the Linux kernel, the following vulnerability has been resolved: net: qualcomm: rmnet: validate MAP frame length before ingress parsing When ingress deaggregation is disabled, rmnet_map_ingress_handler() passes the skb straight to __rmnet_map_ingress_handler(), skipping the length validation that rmnet_map_deaggregate() performs on the aggregated path. The parser then dereferences the MAP header and csum header/trailer based on the on-wire pkt_len without checking skb- >len, so a short frame is read out of bounds: BUG: KASAN: slab-out-of-bounds in rmnet_map_checksum_downlink_packet Read of size 1 at addr ffff88801118ed00 by task exploit/147 Call Trace: ... rmnet_map_checksum_downlink_packet (drivers/net/ethernet/qualcomm/rmnet/rmnet_map_data.c:413) __rmnet_map_ingress_handler (drivers/net/ethernet/qualcomm/rmnet/rmnet_handlers.c:96) rmnet_rx_handler (drivers/net/ethernet/qualcomm/rmnet/rmnet_handlers.c:129) __netif_receive_skb_core.constprop.0 (net/core/dev.c:6089) netif_receive_skb (net/core/dev.c:6460) tun_get_user (drivers/net/tun.c:1955) tun_chr_write_iter (drivers/net/tun.c:2001) vfs_write (fs/read_write.c:688) ksys_write (fs/read_write.c:740) do_syscall_64 (arch/x86/entry/syscall_64.c:94) ... Factor that validation out of rmnet_map_deaggregate() into rmnet_map_validate_packet_len() and run it on the no-aggregation path too. The MAP header is bounds-checked first, since this path can receive a frame shorter than the header. 2026-07-27 7.3 CVE-2026-64550 Linux--Linux In the Linux kernel, the following vulnerability has been resolved: perf/core: Detach event groups during remove_on_exec perf_event_remove_on_exec() removes events by calling perf_event_exit_event(). For top-level events, this removes the event from the context with DETACH_EXIT only. This can leave inconsistent group state when a removed event is a group leader and the group contains siblings without remove_on_exec. If the group was active, the surviving siblings can remain active and attached to the removed leader's sibling list, but are no longer represented by a valid group leader on the PMU context active lists. A later close of the removed leader uses DETACH_GROUP and can promote the still-active siblings from this stale group state. The next schedule-in can then add an already-linked active_list entry again, corrupting the PMU context active list. With DEBUG_LIST enabled, this is caught as a list_add double-add in merge_sched_in(). Fix this by detaching group relationships when remove_on_exec removes an event. This preserves the existing task-exit and revoke behavior, while ensuring surviving siblings are ungrouped before the removed event leaves the context. 2026-07-29 7.8 CVE-2026-64556 Linux--Linux In the Linux kernel, the following vulnerability has been resolved: s390/pkey: Check length in pkey_pckmo handler implementation Explicitly check the length of the target buffer in the pkey_pckmo implementation of the key_to_protkey() handler function. The handler function fails, if the generated output data exceeds the length of the provided target buffer. 2026-07-29 7.8 CVE-2026-64558 Linux--Linux In the Linux kernel, the following vulnerability has been resolved: s390/pkey: Check length in PKEY_VERIFYPROTK ioctl Explicitly check the buffer length request structure provided by user-space and fail, if it exceeds the buffer size. 2026-07-29 7.8 CVE-2026-64559 Linux--Linux In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: Prevent UAF caused by non-leader exec() race Wongi and Jungwoo decoded and reported a non-leader exec() related race which can result in an UAF: sys_timer_delete() exec() posix_cpu_timer_del() // Observes old leader p = pid_task(pid, pid_type); de_thread() switch_leader(); release_task(old_leader) __exit_signal(old_leader) sighand = lock(old_leader, sighand); posix_cpu_timers*_exit(); sighand = lock_task_sighand(p) unhash_task(old_leader); sh = lock(p, sighand) old_leader- >sighand = NULL; unlock(sighand); (p- >sighand == NULL) unlock(sh) return NULL; // Returns without action if(!sighand) return 0; free_posix_timer(); This is "harmless" unless the deleted timer was armed and enqueued in p- >signal because on exec() a TGID targeted timer is inherited. As sys_timer_delete() freed the underlying posix timer object run_posix_cpu_timers() or any timerqueue related add/delete operations on other timers will access the freed object's timerqueue node, which results in an UAF. There is a similar problem vs. posix_cpu_timer_set(). For regular posix timers it just transiently returns -ESRCH to user space, but for the use case in do_cpu_nanosleep() it's the same UAF just that the k_itimer is allocated on the stack. Also posix_cpu_timer_rearm() fails to rearm the timer, which means it stops to expire. While debating solutions Frederic pointed out another problem: posix_cpu_timer_del(tmr) __exit_signal(p) posix_cpu_timers*_exit(p); unhash_task(p); p- >sighand = NULL; sh = lock_task_sighand(p) sighand = p- >sighand; if (!sighand) return NULL; lock(sighand); if (!sh) WARN_ON_ONCE(timer_queued(tmr)); On weakly ordered architectures it is not guaranteed that posix_cpu_timer_del() will observe the stores in posix_cpu_timers*_exit() when p- >sighand is observed as NULL, which means the WARN() can be a false positive. Solve these issues by: 1) Changing the store in __exit_signal() to smp_store_release(). 2) Adding a smp_acquire__after_ctrl_dep() into the !sighand path of lock_task_sighand(). 3) Creating a helper function for looking up the task and locking sighand which does not return when sighand == NULL. Instead it retries the task lookup and only if that fails it gives up. 4) Using that helper in the three affected functions. #1/#2 ensures that the reader side which observes sighand == NULL also observes all preceeding stores, i.e. the stores in posix_cpu_timers*_exit() and the ones in unhash_task(). #3 ensures that the above described non-leader exec() situation is handled gracefully. When the task lookup returns the old leader, but sighand == NULL then it retries. In the non-leader exec() case the subsequent task lookup will observe the new leader due to #1/#2. In normal exit() scenarios the subsequent lookup fails. When the task lookup fails, the function also checks whether the timer is still enqueued and issues a warning if that's the case. Unfortunately there is nothing which can be done about it, but as the task is already not longer visible the timer should not be accessed anymore. This check also requires memory ordering, which is not provided when the first lookup fails. To achieve that the check is preceeded by a smp_rmb() which pairs with the smp_wmb() in write_seqlock() in __exit_signal(). That ensures that the stores in posix_cpu_timers*_exit() are visible. The history of the non-leader exec() issue goes back to the early days of posix CPU timers, which stored a pointer to the group leader task in the timer. That obviously fails when a non-leader exec() switches the leader. commit e0a70217107e ("posix-cpu-timers: workaround to suppress the problems with mt exec") added a temporary workaround for that in 2010 which surv ---truncated--- 2026-07-29 7.8 CVE-2026-64560 litestar-org--litestar Litestar is an Asynchronous Server Gateway Interface (ASGI) framework. Prior to version 2.20.0, Litestar instances which use a template engine in conjunction with CSRF protection are vulnerable to HTML Injection which can be escalated to Cross Site Scripting due to the contents of the CSRF cookie being excluded from automatic escaping by the template engine when configured inline with documentation recommendations. This issue has been patched in version 2.20.0. 2026-07-28 8.1 CVE-2026-48060 magepeopleteam--Booking and Rental Manager Unauthenticated Other Vulnerability Type in Booking and Rental Manager by(), so Laravel derived a constant cache key (md5('authentication')) shared by every request. An unauthenticated attacker sending roughly ten requests per minute from a single IP, most cheaply against the checkpoint endpoint (which has no reCAPTCHA), exhausts the shared counter and causes HTTP 429 for every user attempting to log in or complete two-factor authentication, a panel-wide authentication denial of service that also locks out administrators. This issue is fixed in version 1.13.0. 2026-07-28 7.5 CVE-2026-61609 pterodactyl--wings Wings is the server control plane for Pterodactyl, a free, open-source game server management panel. Prior to 1.12.3, {{config.}} placeholders in egg configuration-file templates allow a low-privileged user to read {{config.token}}, {{config.token_id}}, and {{config.docker.registries}} from the full daemon configuration. This issue is fixed in version 1.12.3. 2026-07-31 9.9 CVE-2026-52855 pterodactyl--wings Wings is the server control plane for Pterodactyl, a free, open-source game server management panel. Prior to 1.13.0, a malformed packet received during the SFTP connection handshake causes a Go panic. This issue is fixed in version 1.13.0. 2026-07-31 7.5 CVE-2026-52856 QuantumCloud--Simple Link Directory Pro Unauthenticated Server Side Request Forgery (SSRF) in Simple Link Directory Pro 'post'`, any author-level user who has authored a `wwp_requests` post - such as one created via the wholesale registration form - can access this nonce and submit the role-assignment request. 2026-07-29 8.8 CVE-2026-12144 savonrb--savon Savon is a Ruby SOAP client. From 0.9.8 until 2.17.2, Savon::Model .all_operations interpolates attacker-controlled WSDL operation names into Ruby source passed to module_eval, allowing Ruby code execution in the application process. This issue is fixed in version 2.17.2. 2026-07-31 8.1 CVE-2026-53510 Sender--Sender Newsletter, SMS and Email Marketing Automation for WooCommerce Administrator SQL Injection in Sender - Newsletter, SMS and Email Marketing Automation for WooCommerce subscribe() callback after it had already called params- >notify(conn, params, NULL, 0). Per the public GATT API, a notify callback with NULL data is the documented signal that the subscription has terminated and the bt_gatt_subscribe_params struct may be freed or reused by the application; calling subscribe() on the struct afterwards is a use-after-free, including an indirect call through the freed params- >subscribe function pointer. The error branch is remotely (adjacent) reachable: a Zephyr device acting as a GATT client that calls bt_gatt_subscribe() can be driven into this ordering when a connected GATT server peer answers the CCC write with an ATT Error Response (the peer-supplied error code flows through att_error_rsp - > att_handle_rsp into gatt_write_ccc_rsp). For applications that free or recycle subscription parameters in their notification-termination handler, this results in memory corruption, a crash (denial of service), or potentially attacker-influenced control flow. The fix reorders the handler so the subscribe() callback runs before the terminating notify(NULL) in both the error and unsubscribe paths. 2026-07-31 7.6 CVE-2026-10685 zephyrproject--zephyr The OCPP 1.6 client in subsys/net/lib/ocpp parsed inbound WAMP RPC frames in parse_rpc_msg() (subsys/net/lib/ocpp/ocpp_j.c) using a hand-rolled helper, extract_string_field(), that copied the message's uid and action fields with strncpy(out_buf, token + 1, outlen - 1) and then scanned the result with strchr(out_buf, '"'). Because strncpy does not NUL-terminate the destination when the source is at least outlen - 1 (127) bytes long, the subsequent strchr reads past the 128-byte destination buffer into adjacent stack memory; if a " byte is found beyond the buffer, a one-byte out-of-bounds NUL write also occurs. A related defect in extract_payload() runs strchr/strrchr over the receive buffer, which may not be NUL-terminated when a maximal-length frame fills it. The parsed bytes come directly from the OCPP central-system server over a websocket: the reader thread fills recv_buf via websocket_recv_msg() and calls parse_rpc_msg() on each inbound DATA frame (subsys/net/lib/ocpp/ocpp.c). A malicious or compromised central server, or an on-path attacker (OCPP is commonly deployed over plain ws://), can send an RPC frame whose uid or action field is 127+ bytes with no closing quote, triggering the out-of-bounds access. The primary impact is a remotely triggerable denial of service: the unbounded scan can fault on an unmapped page, and the stray NUL write can corrupt adjacent stack state. The over-read data is not reflected to the peer, so disclosure is limited. The feature is EXPERIMENTAL and must be explicitly enabled (CONFIG_OCPP). The fix replaces the manual parser with the bounds-respecting json_mixed_arr_parse() and copies the extracted uid with an explicitly NUL-terminated buffer, eliminating both over-reads. 2026-08-02 7 CVE-2026-10848 zip-lib--zip-lib Versions of the package zip-lib before 1.1.0 are vulnerable to Directory Traversal via the caching mechanism for path validation during the extraction process. An attacker can bypass security checks designed to prevent directory traversal. The intended security function, isOutsideTargetFolder, only checks and caches the path status when the initial directory symlink is created during the first extraction. 2026-07-28 7.5 CVE-2026-17524 Back to top Medium Vulnerabilities PrimaryVendor -- Product Description Published CVSS Score Source Info 100plugins--Open User Map Contributor Cross Site Scripting (XSS) in Open User Map prepare() or any integer casting. Additionally, the nonce verification check is performed after the SQL query has already executed, providing no protection against the injection. This makes it possible for authenticated attackers with subscriber-level access and above to inject arbitrary SQL commands, potentially leading to unauthorized extraction of sensitive database contents including user credentials and configuration data. 2026-07-28 6.5 CVE-2026-6251 chrisvrichardson--MapPress Maps for WordPress Unauthenticated Sensitive Data Exposure in MapPress Maps for WordPress prepare(). The wp_unslash() call explicitly removes the backslash escaping that WordPress's wp_magic_quotes() adds to all $_POST data, neutralizing the only layer of SQL injection protection. The sanitize_text_field() function applied afterward offers no SQL protection. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries to the existing query. 2026-08-01 6.5 CVE-2026-6453 CyberTimon--RapidRAW RapidRAW before 1.6.0 does not validate the lutPath field in preset files before passing it to File::open() in lut_processing.rs. On Windows, a UNC path in lutPath causes an outbound SMB connection to an attacker-controlled host, leaking the victim's NTLMv2 credentials. The vulnerable code path is reachable through two vectors: community presets fetched automatically from the remote preset repository when the victim opens the Community tab, and individual preset files imported directly by the victim via the preset import feature (handle_import_presets_from_file in file_management.rs). The second vector does not require control of the community preset repository and is triggered when a user imports a preset file shared through Discord, forums, or similar channels. 2026-07-30 6.5 CVE-2026-64816 DaveGamble--cJSON cJSON through 1.7.19 contains an inefficient algorithmic complexity flaw in cJSON_Compare(). When comparing objects, the function recurses into each shared subtree twice, once in each direction, with no depth guard, making the running time exponential in nesting depth. A small, deeply nested document of a few hundred bytes (depth around 40) compared for equality consumes hours of CPU, and the cost roughly doubles with each additional level of nesting. An application that calls cJSON_Compare() on attacker-influenced JSON that is structurally equal to a reference document is exposed to a denial-of-service condition. 2026-07-29 5.9 CVE-2026-67216 DaveGamble--cJSON cJSON through 1.7.19 applies RFC 6902 JSON Patch operations non-atomically in apply_patch() in cJSON_Utils.c. For a replace operation that is missing its value member, or a move operation whose destination path cannot be resolved, the existing target member is detached and deleted before the operation is fully validated, so the target document is mutated while cJSONUtils_ApplyPatches() or cJSONUtils_ApplyPatchesCaseSensitive() returns a failure status. An attacker who can supply the patch document can destroy addressable members of the target document even though the API reports that the patch failed, defeating the all-or-nothing behavior callers rely on to reject bad patches. 2026-07-29 5.3 CVE-2026-67217 davejesch--Database Collation Fix The Database Collation Fix plugin for WordPress is vulnerable to time-based SQL Injection via the 'force-collation-algorithm' parameter in all versions up to, and including, 1.2.10 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Exploitation requires a trigger.txt file to be present in the plugin's directory (/wp-content/plugins/database-collation-fix/trigger.txt), a condition created by DesktopServer integration events such as site creation, copy, import, move, export, or deploy. 2026-08-01 5.3 CVE-2026-15018 decidim--decidim Decidim is a participatory democracy framework. Prior to 0.30.9, from 0.31.0 before 0.31.5, and in 0.32.0.rc1 before 0.32.0.rc2, the normal download_your_data flow requires the requester to be logged in as the export owner, but the resulting Active Storage blob redirect URL can be replayed without authentication by anyone who obtains it. This is because Decidim::DownloadYourDataController#download_file authenticates the export owner but redirects to a signed Active Storage blob URL that is no longer bound to the owner session. This issue is fixed in versions 0.30.9, 0.31.5, and 0.32.0.rc2. 2026-07-31 6.5 CVE-2026-45377 decidim--decidim Decidim is a participatory democracy framework. From 0.31.1 before 0.31.5 and in 0.32.0.rc1 before 0.32.0.rc2, a participant can directly load /admin/demographics/questions/edit_questions and reach the demographics questionnaire editor without the required administrator authorization. The demographics questionnaire editor should require admin access, but the route under /admin/demographics/questions renders the editor interface without checking whether the caller is an admin. A normal participant can load the page and see the live update form action, which proves the protected interface is reachable. This issue is fixed in versions 0.31.5 and 0.32.0.rc2. 2026-07-31 5.4 CVE-2026-45086 decidim--decidim Decidim is a participatory democracy framework. Prior to 0.30.9, from 0.31.0 before 0.31.5, and in 0.32.0.rc1 before 0.32.0.rc2, the GET /admin/organization/users search interpolates params[:term] into raw Arel.sql ORDER BY similarity expressions before sanitization, allowing an authenticated organization administrator to execute blind PostgreSQL expressions and infer data through timing differences. This issue is fixed in versions 0.30.9, 0.31.5, and 0.32.0.rc2. 2026-07-31 5.5 CVE-2026-45376 decidim--decidim Decidim is a participatory democracy framework. Prior to 0.30.9, from 0.31.0 before 0.31.5, and in 0.32.0.rc1 before 0.32.0.rc2, the identity-document verification admin controllers load pending Authorization records by raw identifier without confirming current_organization ownership, allowing an administrator from one tenant to view, approve, or reject another tenant's ID-document request. This issue is fixed in versions 0.30.9, 0.31.5, and 0.32.0.rc2. 2026-07-31 4.9 CVE-2026-45330 deveasel--Demi One Click Demo Import, Backup & Site Migration The Demi - One Click Demo Import, WP Backup & Site Migration plugin for WordPress is vulnerable to Arbitrary Directory Copy in all versions up to, and including, 0.0.8 via the handle_restore_step function. This is due to missing HTTP access controls on the wp-content/uploads/demi-backup-state/ directory, which exposes the cryptographic restore key used to both authenticate the unauthenticated AJAX handler and forge signed restore-state envelopes. This makes it possible for unauthenticated attackers to copy arbitrary files to attacker-controlled destinations on the server. An active restore operation must have been initiated, which writes the .restore_key and .restore_step_token files to the public upload directory, before the exposed secrets can be harvested and chained to achieve unauthenticated arbitrary file copy. 2026-07-28 5.3 CVE-2026-15012 devitemsllc--ShopLentor All-in-One WooCommerce Growth & Store Enhancement Plugin The ShopLentor - All-in-One WooCommerce Growth & Store Enhancement Plugin plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 3.4.5 via the 'optionSection' parameter due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with contributor-level access and above, to read arbitrary wp_options rows - including internal plugin news feed data, WooCommerce block pattern transients, and third-party configuration records - whose values are stored as arrays-of-arrays containing 'title' keys, enabling cross-plugin data leakage. 2026-07-28 4.3 CVE-2026-16797 devitemsllc--ShopLentor All-in-One WooCommerce Growth & Store Enhancement Plugin The ShopLentor - All-in-One WooCommerce Growth & Store Enhancement Plugin plugin for WordPress is vulnerable to time-based SQL Injection via the 'orderby' parameter in all versions up to, and including, 3.4.5 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. 2026-07-28 4.9 CVE-2026-16811 dfir-iris--iris-web The IRIS web application in version 2.4.26 and possibly others does not protect its MFA validation against brute-force attacks. 2026-07-30 5.9 CVE-2026-16971 dfir-iris--iris-web The IRIS web application in version 2.4.26 and possibly others does not protect its user authentication against brute-force attacks. 2026-07-30 5.9 CVE-2026-18362 dfir-iris--iris-web The IRIS web application in version 2.4.26 and possibly others contains a logout functionality which is ineffective. Stolen session cookies can therefore be misused for a long time. 2026-07-30 4.2 CVE-2026-16970 dotonpaper--Pinpoint Booking System Version 2 The Pinpoint Booking System - Version 2 plugin for WordPress is vulnerable to blind SQL Injection via the 'field' parameter in all versions up to, and including, 2.9.9.6.9 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The nonce required to reach the vulnerable endpoint is emitted on all plugin admin pages loaded under manage_options, making it trivially obtainable by any authenticated administrator. 2026-08-01 4.9 CVE-2026-15403 drakkan--SFTPGo SFTPGo prior to 2.7.4 contains a permission bypass vulnerability that allows authenticated users to circumvent per-directory access controls by creating symbolic links in a permitted directory that point to files in directories where download, upload, or overwrite permissions are denied. Attackers can exploit the create_symlinks permission combined with read and write access in one directory to read or modify files in restricted directories, as operations are authorized against the link's directory permissions rather than the dereferenced target's directory permissions. 2026-07-30 4.2 CVE-2026-10031 edge22--GenerateBlocks The GenerateBlocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Dynamic Tag Injection in HTML Attributes in all versions up to, and including, 2.3.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. A Contributor-level attacker can store the malicious payload by placing a dynamic tag such as {{post_meta key:...}} in a non-URL HTML attribute (e.g., title, aria-label, alt, or data-* attributes) of a GenerateBlocks element block, then setting the corresponding unprotected post meta key via the Custom Fields metabox to a value containing a closing quote and an injected event-handler attribute. 2026-08-01 6.4 CVE-2026-13458 eLyiN--gemini-bridge gemini-bridge is a lightweight MCP server bridging AI agents to Google's Gemini AI via the official CLI. From 1.0.0 until 1.3.1, consult_gemini_with_files in inline mode read any file path supplied in the files argument without confining it to the working directory, then forwarded the contents to the Gemini CLI. Because the caller also controls query, the file contents are echoed back through the Gemini round-trip (and sent to Google), making this an arbitrary local file read. This issue is fixed in version 1.3.1. 2026-07-31 6.2 CVE-2026-54785 facturadorvirtual--Facturacin Electrnica Costa Rica The Facturación Electrónica Costa Rica plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.0.2. This is due to missing or incorrect nonce validation on the (global scope, included by fvcr_admin_page_html) function. This makes it possible for unauthenticated attackers to modify the plugin's configuration, including API tokens, access tokens, economic activity, Hacienda environment mode, invoice and ticket emission flags, exchange rate, and branch settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. 2026-07-29 4.3 CVE-2026-9720 Flipper Code--WP Maps Insertion of Sensitive Information Into Sent Data vulnerability in Flipper Code WP Maps allows Retrieve Embedded Sensitive Data. This issue affects WP Maps: from n/a through 4.9.6. 2026-07-31 4.3 CVE-2026-28144 foomagoo--Plugin Organizer The Plugin Organizer plugin for WordPress is vulnerable to SQL Injection via the 'PO_plugin_path' parameter in versions up to, and including, 10.2.4. This is due to insufficient escaping on the user-supplied parameter in the perform_plugin_search() function, where esc_sql() output is passed as the replacement string to preg_replace(), which collapses backslash escapes and defeats the quoting protection; additionally, the AJAX handler lacks both nonce verification and capability checks. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. 2026-07-28 6.5 CVE-2026-15304 Franky--Events Made Easy Unauthenticated Broken Access Control in Events Made Easy prepare() format string, bypassing parameterization entirely. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. 2026-07-28 6.5 CVE-2026-15267 Themeisle--Feedzy Contributor Server Side Request Forgery (SSRF) in Feedzy

Read more »

Emergency Power Maintenance – US-ORD (Chicago)
THIS IS A SCHEDULED EVENT Sep 15, 11:00 - 21:00 UTC Sep 10, 17:27 UTC Scheduled - Power maintenance is being conducted within our ORD2 (Chicago) datacenter between 11:00 UTC and 21:00 UTC on September 15th, 2026. No downtime or impact is expected as backup power is available for all services within this region. If you have questions surrounding this maintenance please open a Support ticket from the Linode Manager."

Read more »

Emergency Power Maintenance – US-ORD (Chicago)
THIS IS A SCHEDULED EVENT Sep 15, 11:00 - 21:00 UTC Sep 10, 17:27 UTC Scheduled - Power maintenance is being conducted within our ORD2 (Chicago) datacenter between 11:00 UTC and 21:00 UTC on September 15th, 2026. No downtime or impact is expected as backup power is available for all services within this region. If you have questions surrounding this maintenance please open a Support ticket from the Linode Manager."

Read more »

Emergency Power Maintenance – US-ORD (Chicago)
THIS IS A SCHEDULED EVENT Sep 15, 11:00 - 21:00 UTC Sep 10, 17:27 UTC Scheduled - Power maintenance is being conducted within our ORD2 (Chicago) datacenter between 11:00 UTC and 21:00 UTC on September 15th, 2026. No downtime or impact is expected as backup power is available for all services within this region. If you have questions surrounding this maintenance please open a Support ticket from the Linode Manager."

Read more »

Emergency Power Maintenance – US-ORD (Chicago)
THIS IS A SCHEDULED EVENT Sep 15, 11:00 - 21:00 UTC Sep 10, 17:27 UTC Scheduled - Power maintenance is being conducted within our ORD2 (Chicago) datacenter between 11:00 UTC and 21:00 UTC on September 15th, 2026. No downtime or impact is expected as backup power is available for all services within this region. If you have questions surrounding this maintenance please open a Support ticket from the Linode Manager."

Read more »

Emergency Power Maintenance – US-ORD (Chicago)
THIS IS A SCHEDULED EVENT Sep 15, 11:00 - 21:00 UTC Sep 10, 17:27 UTC Scheduled - Power maintenance is being conducted within our ORD2 (Chicago) datacenter between 11:00 UTC and 21:00 UTC on September 15th, 2026. No downtime or impact is expected as backup power is available for all services within this region. If you have questions surrounding this maintenance please open a Support ticket from the Linode Manager."

Read more »

Emergency Power Maintenance – US-ORD (Chicago)
THIS IS A SCHEDULED EVENT Sep 15, 11:00 - 21:00 UTC Sep 10, 17:27 UTC Scheduled - Power maintenance is being conducted within our ORD2 (Chicago) datacenter between 11:00 UTC and 21:00 UTC on September 15th, 2026. No downtime or impact is expected as backup power is available for all services within this region. If you have questions surrounding this maintenance please open a Support ticket from the Linode Manager."

Read more »

Issues Editing Bulk Redirects
Sep 10, 15:59 UTCIdentified - The issue has been identified and a fix is being implemented.Sep 10, 15:41 UTCInvestigating - Cloudflare is aware of and investigating an issue preventing users from adding new redirects to existing Bulk Redirects. Traffic processed by existing Bulk Redirects remains unaffected, and this issue is limited to the configuration of these rules. Further details will be provided as we investigate.

Read more »

Issues Editing Bulk Redirects
Sep 10, 15:59 UTCIdentified - The issue has been identified and a fix is being implemented.Sep 10, 15:41 UTCInvestigating - Cloudflare is aware of and investigating an issue preventing users from adding new redirects to existing Bulk Redirects. Traffic processed by existing Bulk Redirects remains unaffected, and this issue is limited to the configuration of these rules. Further details will be provided as we investigate.

Read more »

Issues Editing Bulk Redirects
Sep 10, 15:59 UTCIdentified - The issue has been identified and a fix is being implemented.Sep 10, 15:41 UTCInvestigating - Cloudflare is aware of and investigating an issue preventing users from adding new redirects to existing Bulk Redirects. Traffic processed by existing Bulk Redirects remains unaffected, and this issue is limited to the configuration of these rules. Further details will be provided as we investigate.

Read more »

Issues Editing Bulk Redirects
Sep 10, 15:59 UTCIdentified - The issue has been identified and a fix is being implemented.Sep 10, 15:41 UTCInvestigating - Cloudflare is aware of and investigating an issue preventing users from adding new redirects to existing Bulk Redirects. Traffic processed by existing Bulk Redirects remains unaffected, and this issue is limited to the configuration of these rules. Further details will be provided as we investigate.

Read more »

Issues Editing Bulk Redirects
Sep 10, 15:59 UTCIdentified - The issue has been identified and a fix is being implemented.Sep 10, 15:41 UTCInvestigating - Cloudflare is aware of and investigating an issue preventing users from adding new redirects to existing Bulk Redirects. Traffic processed by existing Bulk Redirects remains unaffected, and this issue is limited to the configuration of these rules. Further details will be provided as we investigate.

Read more »

Issues Editing Bulk Redirects
Sep 10, 15:59 UTCIdentified - The issue has been identified and a fix is being implemented.Sep 10, 15:41 UTCInvestigating - Cloudflare is aware of and investigating an issue preventing users from adding new redirects to existing Bulk Redirects. Traffic processed by existing Bulk Redirects remains unaffected, and this issue is limited to the configuration of these rules. Further details will be provided as we investigate.

Read more »

PHX (Phoenix) on 2026-09-14
Sep 10, 14:30 UTCScheduled - We will be performing scheduled maintenance in PHX (Phoenix) datacenter on 2026-09-14 between 06:30 and 14:30 UTC. Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in this location, please make sure you are expecting this traffic to fail over elsewhere during this maintenance window as network interfaces in this datacentre may become temporarily unavailable. You can now subscribe to these notifications via Cloudflare dashboard and receive these updates directly via email, PagerDuty and webhooks (based on your plan): https://developers.cloudflare.com/notifications/notification-available/#cloudflare-status.

Read more »

DNS Update Delays
Sep 10, 13:58 UTCInvestigating - Cloudflare is investigating delays in propagation of updates to DNS records. More updates to follow shortly.

Read more »

Japan SMS Carrier Partner Maintenance
THIS IS A SCHEDULED EVENT Sep 29, 06:00 - 07:00 PDT Sep 10, 06:28 PDT Scheduled - Our SMS carrier partner in Japan is conducting a planned maintenance from 29 September 2026 at 06:00 PDT until 29 September 2026 at 07:00 PDT. During the maintenance window, there could be intermittent delays delivering SMS to and from Japan handsets.

Read more »

iPort Connect Dock for iPad for $150
This dock suits anyone who wants a permanent charging and display station for an iPad, like at a reception desk or on a kitchen counter, though there's no discount to note since it's currently priced the same as its $150 list price. Buy Now at Best Buy Features Fast Power Delivery charging Dedicated iPad charging dock Reduces downtime for field devices Secure fit for Connect Cases Versatile hotel, office, or industrial use

Read more »

iPort Connect Dock for iPad for $150
This dock suits anyone who wants a permanent charging and display station for an iPad, like at a reception desk or on a kitchen counter, though there's no discount to note since it's currently priced the same as its $150 list price. Buy Now at Best Buy Features Fast Power Delivery charging Dedicated iPad charging dock Reduces downtime for field devices Secure fit for Connect Cases Versatile hotel, office, or industrial use

Read more »

iPort Connect Dock for iPad for $150
This dock suits anyone who wants a permanent charging and display station for an iPad, like at a reception desk or on a kitchen counter, though there's no discount to note since it's currently priced the same as its $150 list price. Buy Now at Best Buy Features Fast Power Delivery charging Dedicated iPad charging dock Reduces downtime for field devices Secure fit for Connect Cases Versatile hotel, office, or industrial use

Read more »

iPort Connect Dock for iPad for $150
This dock suits anyone who wants a permanent charging and display station for an iPad, like at a reception desk or on a kitchen counter, though there's no discount to note since it's currently priced the same as its $150 list price. Buy Now at Best Buy Features Fast Power Delivery charging Dedicated iPad charging dock Reduces downtime for field devices Secure fit for Connect Cases Versatile hotel, office, or industrial use

Read more »

iPort Connect Dock for iPad for $150
This dock suits anyone who wants a permanent charging and display station for an iPad, like at a reception desk or on a kitchen counter, though there's no discount to note since it's currently priced the same as its $150 list price. Buy Now at Best Buy Features Fast Power Delivery charging Dedicated iPad charging dock Reduces downtime for field devices Secure fit for Connect Cases Versatile hotel, office, or industrial use

Read more »

iPort Connect Dock for iPad for $150
This dock suits anyone who wants a permanent charging and display station for an iPad, like at a reception desk or on a kitchen counter, though there's no discount to note since it's currently priced the same as its $150 list price. Buy Now at Best Buy Features Fast Power Delivery charging Dedicated iPad charging dock Reduces downtime for field devices Secure fit for Connect Cases Versatile hotel, office, or industrial use

Read more »

iPort Connect Dock for iPad for $150
This dock suits anyone who wants a permanent charging and display station for an iPad, like at a reception desk or on a kitchen counter, though there's no discount to note since it's currently priced the same as its $150 list price. Buy Now at Best Buy Features Fast Power Delivery charging Dedicated iPad charging dock Reduces downtime for field devices Secure fit for Connect Cases Versatile hotel, office, or industrial use

Read more »

iPort Connect Dock for iPad for $150
This dock suits anyone who wants a permanent charging and display station for an iPad, like at a reception desk or on a kitchen counter, though there's no discount to note since it's currently priced the same as its $150 list price. Buy Now at Best Buy Features Fast Power Delivery charging Dedicated iPad charging dock Reduces downtime for field devices Secure fit for Connect Cases Versatile hotel, office, or industrial use

Read more »

iPort Connect Dock for iPad for $150
This dock suits anyone who wants a permanent charging and display station for an iPad, like at a reception desk or on a kitchen counter, though there's no discount to note since it's currently priced the same as its $150 list price. Buy Now at Best Buy Features Fast Power Delivery charging Dedicated iPad charging dock Reduces downtime for field devices Secure fit for Connect Cases Versatile hotel, office, or industrial use

Read more »

iPort Connect Dock for iPad for $150
This dock suits anyone who wants a permanent charging and display station for an iPad, like at a reception desk or on a kitchen counter, though there's no discount to note since it's currently priced the same as its $150 list price. Buy Now at Best Buy Features Fast Power Delivery charging Dedicated iPad charging dock Reduces downtime for field devices Secure fit for Connect Cases Versatile hotel, office, or industrial use

Read more »

iPort Connect Dock for iPad for $150
This dock suits anyone who wants a permanent charging and display station for an iPad, like at a reception desk or on a kitchen counter, though there's no discount to note since it's currently priced the same as its $150 list price. Buy Now at Best Buy Features Fast Power Delivery charging Dedicated iPad charging dock Reduces downtime for field devices Secure fit for Connect Cases Versatile hotel, office, or industrial use

Read more »

iPort Connect Dock for iPad for $150
This dock suits anyone who wants a permanent charging and display station for an iPad, like at a reception desk or on a kitchen counter, though there's no discount to note since it's currently priced the same as its $150 list price. Buy Now at Best Buy Features Fast Power Delivery charging Dedicated iPad charging dock Reduces downtime for field devices Secure fit for Connect Cases Versatile hotel, office, or industrial use

Read more »

iPort Connect Dock for iPad for $150
This dock suits anyone who wants a permanent charging and display station for an iPad, like at a reception desk or on a kitchen counter, though there's no discount to note since it's currently priced the same as its $150 list price. Buy Now at Best Buy Features Fast Power Delivery charging Dedicated iPad charging dock Reduces downtime for field devices Secure fit for Connect Cases Versatile hotel, office, or industrial use

Read more »

iPort Connect Dock for iPad for $150
This dock suits anyone who wants a permanent charging and display station for an iPad, like at a reception desk or on a kitchen counter, though there's no discount to note since it's currently priced the same as its $150 list price. Buy Now at Best Buy Features Fast Power Delivery charging Dedicated iPad charging dock Reduces downtime for field devices Secure fit for Connect Cases Versatile hotel, office, or industrial use

Read more »

iPort Connect Dock for iPad for $150
This dock suits anyone who wants a permanent charging and display station for an iPad, like at a reception desk or on a kitchen counter, though there's no discount to note since it's currently priced the same as its $150 list price. Buy Now at Best Buy Features Fast Power Delivery charging Dedicated iPad charging dock Reduces downtime for field devices Secure fit for Connect Cases Versatile hotel, office, or industrial use

Read more »