It's a Log4j bug, and you ought to patch it. But we don't think it's a critical crisis like the last one.