20 apt updates

and one of them was freepbx17..

Why is that an apt update package and not updated through freepbx itself like usual updates… last time sangoma did that, I had to fwconsole ma install a,b,c,d,e,f,g,h because it fscked something, just seems strange apt wants to install a 249mb freepbx when it self updates itself… is this more sangoma doesnt know debian, or is there a reason this is happening. (I’m not a debian shop so I don’t profess to know it either)

Edited after fixing a heap of things and refreshing sigs I think this freepbx17 should have been added to a blacklist when it installed itself since it installed older and yes the vulnerable endpoint which ive now processed a REMOVE on.

oh yeah, and whats with all these node packages that cant be updated unless manually? (but theyve always been around, just the list is growing lol)

The following modules are disabled because they need to be upgraded:
framework

You should go to the module admin page to fix these.

So the apt downgraded endpoint and now rightfully throws need upgrade error? W T A F we did that 2 days ago!

endpoint (Cur v. 17.0.2.26) should be upgraded to v. 17.0.3 to fix security issues: GHSA-m42g-xg4c-5f3h