XPost: alt.comp.os.windows-11   
   From: winstonmvp@gmail.com   
      
   On 1/28/2026 5:45 PM, J. P. Gilliver wrote:   
   > On 2026/1/28 22:43:36, ...w¡ñ§±¤ñ wrote:   
   >> J. P. Gilliver wrote on 1/28/2026 2:11 PM:   
   >>> On 2026/1/28 16:6:23, ...w¡ñ§±¤ñ wrote:   
   >>> []   
   >>>   
   >>>> - Versions supported are update-able and fixable, as in the past earlier   
   >>>> non-supported versions are not. Likewise, MSFT does not report   
   >>>> vulnerability to versions older than indicated in the CVE.   
   >>>   
   >>> So earlier versions are not fixable (by this patch, anyway), but may not   
   >>> be vulnerable in the first place.   
   >>    It would be wise to assume the opposite => vulnerable   
   >>>   
   >>>> - applies to any malicious Office file => 'whatever' in your terminology   
   >>>   
   >>> When I said does it have to be .docx or whatever, I meant does it have   
   >>> to be (for example) .docx, .xlsx, or whatever, as opposed to .doc, .xls,   
   >>> and so on - i. e. the "new" formats.   
   >>    All those file types can include links or phishing content - not sure   
   >> why you wouldn't know that.   
   >   
   > This thread started about a _specific_ exploit, that MS had released a   
   > patch to protect against.   
      
   The link provided to the CVE specified the exploit parameter as:   
   "An attacker must send a user a malicious Office file and convince them   
   to open it."   
     => should be interpreted as any possible 'Office' file, i.e. no   
   delineation for prior version file extensions.   
      
   --   
   ...w¡ñ§±¤ñ   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)