6 ms·
Not running, but supported. You can check your app with: bin/rails runner ' require "vips" puts "ruby-vips #{Vips::VERSION} libvips #{Vips.ver
by bradly 12d ago
Not running, but supported. You can check your app with:
bin/rails runner '
require "vips"
puts "ruby-vips #{Vips::VERSION} libvips #{Vips.version(0)}.#{Vips.version(1)}.#{Vips.version(2)}"
begin
Vips::Operation.new("matload")
puts "matload PRESENT - this build can reach libmatio"
rescue Vips::Error
puts "matload ABSENT - this build cannot reach libmatio"
end
'
This is from the Rails official docs for the CVE which, interestingly, they only released as an agent skill. https://github.com/rails/rails-forensics-CVE-2026-66066/blob/main/skills/kr2s-was-i-vulnerable/references/guide.md https://github.com/rails/rails-forensics-CVE-2026-66066/blob...
- comrade1234 12d agoWhy would you have matlab on an external server? People don't even have a compiler on the server in this situation. Crazy.
- XenoCyber0 12d agoAn agent skill is the official distribution format for the forensics on a 9.5. I mean, I get it, anyone running a Rails app right now is pasting "am I affected" into an agent anyway, but it's the kind of thing that would've sounded like a joke a couple years ago.
- TeMPOraL 12d agoMakes sense though. Agent skills are - by a mix of LLM nature and fashion - just high-quality documentation. Documentation that only gets written now, because agents are what makes docs "something immediately and directly useful for me right now", vs. "something I should write so others may benefit, someday, somehow". Human incentives are funny.
- XenoCyber0 8d ago[dead]