>>3391721>security fixes on a raw processor/image editorYou just proved not knowing shit about software or computer security, congrats anon.
Allow me to explain, in order for an attacker to exploit a bug in a piece of software, they require a way to interact with that piece of software, an isolated computer program which's only form of input comes from the user and the camera raws isn't going to magically become vulnerable to remote attacks.
Operating systems, web browsers, software running with privileged system permissions, those are vulnerable to attacks, since their input comes from untrusted parties like websites, network and unprivileged system users, an image editor on the other hand only takes the input the user gives it.
The only way an image editor could possibly be exploited by an attacker is if the user often opens files from untrusted sources on it, then a specially crafted image/raw files could exploit said software bug, but in order for that to work, the attacker would have to know what software their target was running, what version and would have to social engineer the user to open said file with said program. That of course would be very unlikely to happen, unless you work on a studio and receive files from clients daily (if that's the case just pay the adobe tax, you're making fair money from it anyway) but if you're editing your photos like most people, then don't worry, your camera isn't going to write malicious files to your SD card.
