Should I patch lopdf before updating Ollama and checking OpenAI cost data?

Description and use

<p>If a service accepts PDFs, lopdf 0.41.0 or earlier can abort on a roughly 21 KB crafted file. I'd patch that first, then handle the Windows-specific Ollama runner change, then reconcile OpenAI cost data that was delayed and later recovered.</p> <p><a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fq9s96qohkddscpvvrvrt.png" class="article-body-image-wrapper"><img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%

Problem

<p>If a service accepts PDFs, lopdf 0.41.0 or earlier can abort on a roughly 21 KB crafted file. I'd patch that first, then handle the Windows-specific Ollama runner change, then reconcile OpenAI cost data that was delayed and later recovered.</p> <p><a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fq9s96qohkddscpvvrvrt.png" class="article-body-image-wrapper"><img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%

Outcome

<p>If a service accepts PDFs, lopdf 0.41.0 or earlier can abort on a roughly 21 KB crafted file. I'd patch that first, then handle the Windows-specific Ollama runner change, then reconcile OpenAI cost data that was delayed and later recovered.</p> <p><a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fq9s96qohkddscpvvrvrt.png" class="article-body-image-wrapper"><img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%

Evidence

Should I patch lopdf before updating Ollama and checking OpenAI cost data?

Source