JP1 Automatic Job Management System 3 has a memory overflow flaw
A bug in this job scheduling software lets data written past the end of a memory area, which can crash the service or let an attacker run their own code. Think of it as a container being overfilled so the contents spill into a neighboring o
| Severity | CriticalCVSS 9.4 of 10 |
|---|---|
| Being exploited? | UnclearNo reports either way yet |
| Fix available? | YesUpgrade to 13-50-31 or later · since 27 Oct 2026 |
| How sure is this? | Official sourceBacked by an official source |
What happened
A heap-based buffer overflow in the Manager component of JP1/Automatic Job Management System 3 allows out-of-bounds memory writes in affected versions.
Are you affected?
You are affected if you run JP1/Automatic Job Management System 3 - Manager from version 10-00 before 13-50-31.
JP1/Automatic Job Management System 3 - Manager: 10-00 up to (not including) 13-50-31
What to do
- Check your JP1/Automatic Job Management System 3 Manager version and confirm whether it is between 10-00 and 13-50-31.
- Upgrade the Manager to version 13-50-31 or later.
- Restrict network access to the Manager so only trusted systems can reach it until the upgrade is complete.
Timeline
- 27 Oct 2026, 10:16 UTCPublicly disclosed
- 27 Oct 2026, 10:16 UTCReported by NVD · NVD
- 27 Oct 2026, 10:17 UTCPicked up by Zero Radar
Sources 1 report, oldest first
Official vendor, government CERT or advisory database
- CVE-2026-76937NVD · 27 Oct 2026, 10:16 UTC
Technical details
- ID
- CVE-2026-76937
- CVSS
- 9.4 / 10
- EPSS
- 0.5% chance of exploitation within 30 days
- Disclosed
- 27 Oct 2026, 10:16 UTC
- On Zero Radar
- 27 Oct 2026, 10:17 UTC (1 min after disclosure)
- Last change
- 27 Oct 2026, 10:17 UTC
The plain-language parts and the attack diagram were written by an AI model (anthropic/claude-haiku-5.5) from the sources above. Facts like versions, exploitation and dates come from the sources themselves. How Zero Radar works