Skip to content
Thoughtful, detailed coverage of everything Apple for 34 years
and the TidBITS Content Network for Apple professionals
4 comments

Safari 11.1 (Build 1×605.1.33.1.4)

Apple has released a supplemental edition of Safari 11.1 to patch a pair of vulnerabilities in three builds of the Web browser for the following operating systems: OS X 10.11.6 El Capitan (Safari build 11605.1.33.1.4), macOS 10.12.6 Sierra (Safari build 12605.1.33.1.4), and macOS 10.13.4 High Sierra (Safari build 13605.1.33.1.4, although this version is also bundled with“Security Update 2018-001 (High Sierra),” 25 April 2018). The update eliminates two memory corruption issues in WebKit that could lead to arbitrary code execution when processing maliciously crafted Web content. Safari 11.1 is available only via Software Update. (Free, release notes, macOS 10.11.6+)

Subscribe today so you don’t miss any TidBITS articles!

Every week you’ll get tech tips, in-depth reviews, and insightful news analysis for discerning Apple users. For over 33 years, we’ve published professional, member-supported tech journalism that makes you smarter.

Registration confirmation will be emailed to you.

This site is protected by reCAPTCHA. The Google Privacy Policy and Terms of Service apply.

Comments About Safari 11.1 (Build 1×605.1.33.1.4)

Notable Replies

  1. For High Sierra (10.13), you seem to get this Safari update along with Security Update 2018-001.

    This wasn’t exactly a surprise, but I didn’t see it mentioned in the article (for which I am all the same grateful, as always).

  2. Good note — you’re absolutely right.

    It seems odd that Apple would release this update without even changing the normal version number.

  3. It has to do with future updates. I won’t pretend to understand it all, but know it’s done to prevent confusion for users that failed to run the security update for some reason when macOS 10.13.5 or Safari 11.11.1 or whatever is already in the pipeline is released.

  4. Yeah, I assume as much too. But it feels like a failure of a versioning policy to end up in a situation where this sort of thing happens.

Join the discussion in the TidBITS Discourse forum

Participants

Avatar for ace Avatar for agen Avatar for alvarnell Avatar for clarke