I haven't been following MoAB closely, but I've read over a few, and they all seem to fall into one or more of these categories:
A) Requires local access to the machine.
B) Does nothing but cause an app to unexpectedly quit.
C) Can allow for "arbitrary code execution" in theory, but nobody seems to know how to exploit this in practice. ("Arbitrary" does not mean "predictable" or "controllable".)
D) Requires at least the deployment of a trojan to exploit. Trojans will always be possible to make on any system, period. Deploying them is the only hard part, and I've seen nothing on MoAB to make this any easier.
E) Is not a bug in any of Apple's software, but rather third-party programs. (Why are these in the Month of Apple Bugs to begin with? Could he not fill 30 days with actual Apple bugs even with his low standards?)
None of them seem to be especially dangerous, so none of them demand Apple's immediate attention. Mostly they're just extra-geeky ways to crash programs, with some dangerous-sounding terms like "denial of service" (i.e., a crash) and "potential arbitrary code execution" (which could, and probably does, just mean something completely unpredictable, which would probably manifest itself in an application crash and nothing more).
IMO, it's just insubstantial fear-mongering. It's cute and clever, but really, it makes me feel better about OS X's security, not worse. If these are the worst a dedicated geek can come up with, then hot damn, we're in good shape!
But again, I have not read every entry closely. Is there any one in particular you think deserves immediate attention?